Our review
Optionally checks, then commits code to the current or a new feature branch with conventional commit messages.
Strengths
- Enforces conventional commit format (type(scope): description)
- Optional pre-commit check (lint, build, tests)
- Auto-creates a feature branch if on main
Limitations
- Does not handle merge conflicts
- Automated checks may fail if test environment is not set up
- Sensitive files are excluded, but user still needs to verify
To standardize and safeguard the commit process in teams or structured projects.
For quick, informal commits where convention is overkill or when the check environment is unreliable.
Security analysis
CautionThe skill requires executing git commands and potentially running arbitrary checks (lint, build, test) that may involve custom scripts. While not inherently destructive, it delegates significant execution authority to the AI agent, which could be exploited in a malicious repo context.
- •Instructs running bash commands in parallel, which could include arbitrary build/test execution without explicit safety boundaries.
Examples
Please commit my changes with a conventional commit message. Run checks first.Commit my changes directly without any checks, using force mode.I'm on main, please commit my changes to a new feature branch with a proper commit message.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.