hsablonniere/commit
skills/commit/SKILL.md
Create a git commit with a well-crafted conventional commit message. Use when the user asks to commit, create a commit, or says something like "commit this".
tools
Updated Jun 15, 2026
$ install --global
skillsauthnpx skillsauth add hsablonniere/skills commitInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 15, 2026, 2:23 AM80.3s1 file scanned
SKILL.md
- name:
- commit
- description:
- Create a git commit with a well-crafted conventional commit message. Use when the user asks to commit, create a commit, or says something like "commit this".
- model:
- haiku
- allowed-tools:
- Bash(git:*), Bash(fmt:*), Read
Commit
Create conventional commit messages that explain the why, not the what.
The commit message helps:
- The PR reviewer understand the context quickly
- The devs in 6 months who will
git blamethis code
Workflow
1. Get the staged diff
git diff --cached
If nothing is staged, stop and tell the user to stage changes first.
2. Get existing scopes
Extract scopes already used in the project to stay consistent:
git log --oneline --no-merges | sed -n 's/^[^ ]* [a-z]*(\([^)]*\)).*/\1/p' | sort | uniq -c | sort -rn
Use one of these scopes if it fits. Only invent a new scope if none matches.
3. Analyze the diff
Identify:
- Which files are touched
- Which functions/classes/components are modified
- The pattern of the change (addition, deletion, refactoring, fix...)
If needed, use Read to explore touched files for better architectural understanding.
4. Decide: ask or skip
Skip questions if the why is obvious:
- Bug fix with explicit error message
- Typo / formatting
- Adding tests for existing code
- Rename with clear reason in the code
- The conversation already provides full context (e.g. you just helped implement the change)
Ask 1-2 questions if you need to clarify:
- Refactoring without a visible problem
- New feature without business context
- Non-obvious technical choice
- Behavior change without an apparent bug
Questions must be specific to the diff — mention what you see and ask why:
- "You're migrating from bash to Node.js — was it for performance, maintainability, something else?"
- "You're adding retry with backoff on API X — what was the issue in prod?"
- "You're replacing moment.js with date-fns — bundle size problem?"
Never ask vague questions like "Why this change?" or "What was the problem?".
5. Generate the commit message
Format
type(scope): short description
One or two paragraphs explaining the context and motivation.
Each paragraph is between 125 and 250 characters.
Rules
- Title < 72 characters, english, lowercase
- Types:
feat,fix,docs,style,refactor,test,chore,ci - Body: 1-2 paragraphs, 125-250 chars each
The body explains the WHY
Answer: What problem? Why now? Why this approach?
Forbidden patterns (the diff already shows the what):
- "This change/commit introduces/adds/creates..."
- "This refactors/updates/modifies..."
- Any form of "add X, create X, update X, remove X, rename X, refactor X"
6. Wrap the body
Do not rely on the LLM to respect line length. Wrap the body (not the title) at 80 characters using fmt:
echo "<body>" | fmt -w 80
7. Commit
Always use a HEREDOC to avoid escaping issues:
git commit -F - << 'EOF'
type(scope): description
Wrapped body paragraph.
EOF
Related Skills
hsablonniere/rebase
tools
VerifiedTrustedCommunity
Perform a non-interactive interactive git rebase. Use when the user asks to rebase, squash, reorder, drop, or rename commits.
SKILL.mdUpdated Jun 15, 2026
hsablonniere/pull-request
tools
VerifiedTrustedCommunity
Create a Pull Request (GitHub) or Merge Request (GitLab) with a well-crafted title and description. Use when the user asks to create a PR, MR, open a pull request, submit a merge request, or says something like "open a PR".
SKILL.mdUpdated Jun 15, 2026
hsablonniere/paper-review
development
VerifiedTrustedCommunity
Conversational code review written to a markdown file the reviewer annotates, then acted on. Use when the user asks to review the current branch or diff, runs /paper-review (optionally with "working tree", "staging", "rescan", or a ref/range), says "review my changes", or asks to act on their annotations in an existing review file.
SKILL.mdUpdated Jun 15, 2026
hsablonniere/interview
tools
VerifiedTrustedCommunity
Interview the user to deeply explore an idea, feature, or problem through Q&A. Use when the user asks to be interviewed, wants to think through something, or needs help clarifying a concept.
SKILL.mdUpdated Jun 15, 2026