Our review
Optionally runs checks (lint, build, test) before committing changes with a conventional commit message, creating a new feature branch if on main.
Strengths
- Generates conventional commit messages (type(scope): description) consistently
- Runs a pre-commit check pipeline to catch errors early
- Automatically creates a feature branch to avoid direct commits on main
Limitations
- Does not support partial staging or interactive hunk selection
- Secret files are not excluded automatically, only via heuristic detection
- Commit message style relies on analysis of recent commits, which may vary
Use this skill for quick, clean commits with automatic checks and standardized messages.
Avoid it when you need custom commit messages or granular control over what gets staged.
Security analysis
SafeThe skill only uses standard git commands (status, diff, log, branch, add, commit) and advises against committing secret files. No destructive, obfuscated, or data-exfiltrating actions are instructed.
No concerns found
Examples
Commit my current changes with checks.Force commit the staged changes and skip checks.I am on main. Commit these changes to a new feature branch.name: commit description: Optionally checks, then commits code to the current or a new feature branch.
When asked to commit code, follow these steps:
Arguments
check(default): Run checks first to lint, build, and test the code. Stop if any checks fail.force: Skip the check step and commit directly.
Steps
-
Run these bash commands in parallel to understand the current state:
git statusto see all untracked filesgit diff HEADto see both staged and unstaged changesgit log --oneline -10to see recent commit messages for style consistency
-
If you are on the
mainbranch, create a new feature branch usinggit branchand switch to it. -
Analyze all changes and draft a commit message:
- Summarize the nature of the changes (new feature, enhancement, bug fix, refactoring, test, docs, etc.)
- Use the conventional commit format:
type(scope): description - Keep the first line under 72 characters
- Do not commit files that likely contain secrets (.env, credentials.json, etc.)
-
Stage and commit the changes:
- Add relevant files using
git add - Use a plain string for the commit message (do not use HEREDOCs).
- Add relevant files using
-
Report the results including:
- The commit hash
- The commit message
Next.js App Router Expert
Development
A skill that turns Claude into a Next.js App Router expert.
README Generator
Development
Creates professional and comprehensive README.md files for your projects.
API Documentation Writer
Development
Generates comprehensive API documentation in OpenAPI/Swagger format.