Stats
Actions
Tags
From cipherpowers
Guides systematic git commits: checks staging status, reviews diffs, splits changes into atomic commits, formats conventional messages. Use before PRs or when committing code.
How this skill is triggered — by the user, by Claude, or both
Slash command
/cipherpowers:commit-workflowThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Structured commit process ensuring code quality through pre-commit verification, atomic commit composition, and conventional commit message formatting.
Structured commit process ensuring code quality through pre-commit verification, atomic commit composition, and conventional commit message formatting.
Before committing:
Commit composition:
Note: Quality gates (PostToolUse, SubagentStop hooks) automatically enforce pre-commit checks, so code quality is already verified.
Read these before committing:
${CLAUDE_PLUGIN_ROOT}standards/conventional-commits.md - Commit message format${CLAUDE_PLUGIN_ROOT}standards/git-guidelines.md - Git workflow standardsNote: Pre-commit quality checks (linters, tests, build) are enforced automatically by quality gates (PostToolUse, SubagentStop hooks). By the time you're committing, gates have already verified code quality.
Review what's staged:
git status
If 0 files staged:
git add .git add <specific-files>Understand what's being committed:
# See staged changes
git diff --staged
# See all changes (staged + unstaged)
git diff HEAD
Analyze for logical grouping:
Single commit: All changes are logically related (one feature, one fix)
Multiple commits: Multiple distinct changes detected:
If splitting, stage selectively:
# Stage specific files
git add file1.py file2.py
git commit -m "..."
# Stage remaining files
git add file3.py
git commit -m "..."
Format (from standards/conventional-commits.md):
<type>(<optional-scope>): <description>
[optional body]
[optional footer]
Common types:
feat: New featurefix: Bug fixrefactor: Code change that neither fixes bug nor adds featuredocs: Documentation changestest: Adding or updating testschore: Maintenance tasksExample messages:
git commit -m "feat(auth): add password reset functionality
Implement forgot-password flow with email verification.
Includes rate limiting to prevent abuse."
git commit -m "fix: handle null values in user profile endpoint"
git commit -m "refactor: extract validation logic into separate module
Improves testability and reduces duplication across endpoints."
Execute commit:
git commit -m "type(scope): description"
Verify commit:
git log -1 --stat
NEVER skip:
Common rationalizations that violate workflow:
Note: Pre-commit quality checks are enforced by quality gates automatically - no need to run them manually at commit time.
See test-scenarios.md for pressure tests validating this workflow resists shortcuts.
npx claudepluginhub cipherstash/cipherpowers --plugin cipherpowersGit commit workflow pipeline: atomic unit identification, commit ordering, quality gates, message validation, and post-commit verification. Invoke whenever task involves any interaction with git commits — committing changes, staging work, splitting diffs into atomic units, or preparing work for version control.
Guides git commits with atomic change analysis, conventional commit messages, and interactive staging options. Flags non-atomic commits and suggests splits for better maintainability.
Analyzes git changes, groups into atomic logical commits, writes conventional commit messages, stages files selectively, and commits safely. Use for clean solo git history without blind adds.