Best use case
git-commits is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Git Commit Rules
Teams using git-commits should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/git-commits/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How git-commits Compares
| Feature / Agent | git-commits | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Git Commit Rules
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Git Commit Rules
When the user asks to commit, push, or save changes to git:
## MUST Use /commit Skill
**DO NOT** run `git commit` directly. Instead:
```
Skill("commit")
```
The `/commit` skill:
1. Removes Claude attribution from commits
2. Generates reasoning.md capturing what was tried
3. Clears build attempts for next feature
## Why This Matters
- Regular `git commit` adds "Generated with Claude Code" and Co-Author lines
- The `/commit` skill removes these so commits appear user-authored
- Reasoning capture preserves build history for future sessions
## Trigger Words
When you see these in user prompts, use the commit skill:
- "commit", "push", "save changes"
- "push to github", "push changes"
- "commit and push"
## After Commit
The skill will prompt you to run:
```bash
bash "$CLAUDE_PROJECT_DIR/.claude/scripts/generate-reasoning.sh" <hash> "<message>"
```
Then push if requested:
```bash
git push origin <branch>
```Related Skills
phase-gated-commits
Break large features into phases where each phase follows implement -> review -> commit cycle. Use for multi-file features or refactoring that should have clean git history.
workflow-router
Goal-based workflow orchestration - routes tasks to specialist agents based on user goals
wiring
Wiring Verification
websocket-patterns
Connection management, room patterns, reconnection strategies, message buffering, and binary protocol design.
visual-verdict
Screenshot comparison QA for frontend development. Takes a screenshot of the current implementation, scores it across multiple visual dimensions, and returns a structured PASS/REVISE/FAIL verdict with concrete fixes. Use when implementing UI from a design reference or verifying visual correctness.
verification-loop
Comprehensive verification system covering build, types, lint, tests, security, and diff review before a PR.
vector-db-patterns
Embedding strategies, ANN algorithms, hybrid search, RAG chunking strategies, and reranking for semantic search and retrieval.
variant-analysis
Find similar vulnerabilities across a codebase after discovering one instance. Uses pattern matching, AST search, Semgrep/CodeQL queries, and manual tracing to propagate findings. Adapted from Trail of Bits. Use after finding a bug to check if the same pattern exists elsewhere.
validate-agent
Validation agent that validates plan tech choices against current best practices
tracing-patterns
OpenTelemetry setup, span context propagation, sampling strategies, Jaeger queries
tour
Friendly onboarding tour of Claude Code capabilities for users asking what it can do.
tldr-stats
Show full session token usage, costs, TLDR savings, and hook activity