Our review
Creates atomic git commits for a session's changes with clear messages, without prompting the user for confirmation.
Strengths
- Splits changes into focused, atomic commits instead of one catch-all commit
- Uses the session history to explain why changes were made, not just what changed
- Stages explicit files with git add and excludes the thoughts/ directory
- Runs non-interactively, which suits CI-style execution
Limitations
- Genuinely side-effecting: it won't stop for approval, so mistakes require a manual reset or revert
- The 'Execute upon confirmation' step conflicts with the instruction to never ask for feedback, leaving the expected behaviour slightly ambiguous
- No explicit safeguard against secrets or sensitive files; safety depends on the model's judgement and the stated exclusions
Use when you want the agent to commit this session's work itself as tidy, non-interactive commits, such as in an automated pipeline.
Avoid it when you want to review and approve each commit before it is created, or when the repo has changes the agent cannot reliably distinguish from its own.
Security analysis
CautionThe skill uses Bash to inspect and commit changes non-interactively. It does not instruct destructive or exfiltrating actions, but committing code is a meaningful side effect and the skill explicitly avoids user confirmation, so caution is appropriate.
- •Performs git commit actions without per-commit user confirmation, which can create unintended history if context is misinterpreted.
- •Uses Bash for git operations, a powerful side-effecting tool, though for a legitimate purpose.
- •Relies on model judgment to exclude sensitive or unintended files, with only textual safeguards against committing thoughts/ or dummy files.
Examples
Commit all the changes from this session as atomic commits without asking me for confirmation.Do a CI-style commit pass on the work we just did: group related files into logical commits and skip anything under thoughts/.Review the session diff with git status and git diff, then create clear imperative-mood commits for the files we changed.name: ci_commit description: Create git commits for session changes with clear, atomic messages, without prompting the user for confirmation. Side-effecting; user-only — never auto-invoke. Use when the user asks for a non-interactive (CI-style) commit run. model: sonnet allowed-tools: Bash, Read disable-model-invocation: true
Commit Changes
You are tasked with creating git commits for the changes made during this session.
Process:
-
Think about what changed:
- Review the conversation history and understand what was accomplished
- Run
git statusto see current changes - Run
git diffto understand the modifications - Consider whether changes should be one commit or multiple logical commits
-
Plan your commit(s):
- Identify which files belong together
- Draft clear, descriptive commit messages
- Use imperative mood in commit messages
- Focus on why the changes were made, not just what
-
Execute upon confirmation:
- Use
git addwith specific files (never use-Aor.) - Never commit the
thoughts/directory or anything inside it! - Never commit dummy files, test scripts, or other files which you created or which appear to have been created but which were not part of your changes or directly caused by them (e.g. generated code)
- Create commits with your planned messages until all of your changes are committed with
git commit -m
- Use
Remember:
- You have the full context of what was done in this session
- Group related changes together
- Keep commits focused and atomic when possible
- The user trusts your judgment - they asked you to commit
- IMPORTANT: - never stop and ask for feedback from the user.
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.