Our review
Analyzes current changes and proposes logical, well-structured commits.
Strengths
- Prevents large or mixed-subject commits.
- Presents a clear plan before execution, with room for adjustment.
- Ensures each commit is independently meaningful.
Limitations
- Does not handle merge conflicts or rebases.
- Requires manual confirmation of each planned commit.
When you have multiple unrelated changes in your working directory and want clean, topic-based commits.
For a single obvious commit, or if you are using a GUI versioning tool.
Security analysis
SafeThe skill only uses standard git commands for status, diffing, staging, and committing. It requires user confirmation before any changes are made. There are no destructive or obfuscated actions, no network calls, and no data exfiltration risks.
No concerns found
Examples
Analyze my current git changes and help me commit them in logical chunks.I have changes for a bug fix and a new feature. Can you group them into separate commits?Show me a commit plan for my current changes and wait for my approval before executing.description: Analyze changes and commit in logical chunks allowed-tools: Bash(git *)
Smart Commit
Step 1: Analyze All Changes
!git status
!git diff
!git diff --cached
Step 2: Plan Logical Commits
Group changes by these dimensions:
- Feature work vs refactoring vs bug fixes
- Area/scope (which part of the wiki? config, content, infra, skin, extensions?)
- Content vs infrastructure
- Deps/config vs behavior changes
- Docs vs code
If everything belongs together -> single commit. If changes span multiple concerns -> plan multiple commits.
Step 3: Present the Plan (CONCISE)
Show a brief table - one row per commit group:
| # | Message | Files |
|---|---------|-------|
| 1 | fix(config): correct upload size limit in LocalSettings | 1 file |
| 2 | feat(content): add Poi article draft | 2 files |
Do NOT:
- List every file individually
- Explain what each file does
- Provide detailed breakdowns
- Add commentary about the changes
Just: commit message + file count. User can ask for details if needed.
Wait for confirmation before proceeding.
Step 4: Execute
For each planned commit:
- Stage only the relevant files:
git add <files> - For mixed files, use patch staging:
git add -p <file> - Commit with the planned message
- Verify with
git status
After all commits, show git log --oneline -n <count> to confirm.
Rules
- Never commit unrelated changes together
- If a commit can't be described in one line, it's too broad--split it
- Each commit should be independently meaningful
- Think: "Will this make sense when generating the changelog?"
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.