tobihagemann/commit-rules
codex/skills/commit-rules/SKILL.md
Shared commit message rules and technical constraints referenced by $stage-commit and $commit-staged. Not typically invoked directly.
$ install --global
skillsauthnpx skillsauth add tobihagemann/turbo commit-rulesInstall 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 4, 2026, 5:59 AM111.0s1 file scanned
SKILL.md
- name:
- commit-rules
- description:
- Shared commit message rules and technical constraints referenced by $stage-commit and $commit-staged. Not typically invoked directly.
Commit Rules
Commit Message Rules
- Match the style from
git log -n 10 --oneline - Concise and descriptive
- Imperative mood, present tense
- Aim for ≤100 characters in the subject
- No commit description—summarize everything in the message
- Don't reference
.turbo/content (filenames, requirement IDs, shell references, headings) in commit messages..turbo/is gitignored, so these references would be opaque to anyone reading without local copies.
Technical Constraints
- Use
git commit -m "message"directly—do not use heredoc syntax (sandbox blocks temp file creation) - Never bypass commit signing (
--no-gpg-sign,-c commit.gpgsign=false). If signing fails, userequest_user_inputto let the user resolve it—they may need to approve a key prompt.
Related Skills
tobihagemann/codex-exec
tools
VerifiedTrustedCommunity
Run autonomous task execution using the codex CLI. Use when the user asks to "codex exec", "run codex exec", "execute a task with codex", or "delegate to codex".
334SKILL.mdUpdated May 9, 2026
tobihagemann/finalize
development
VerifiedTrustedCommunity
Run the post-implementation quality assurance workflow including tests, code polishing, review, and commit. Use when the user asks to "finalize implementation", "finalize changes", "wrap up implementation", "finish up", "ready to commit", or "run QA workflow".
331SKILL.mdUpdated May 9, 2026
tobihagemann/finalize
development
VerifiedTrustedCommunity
Run the post-implementation quality assurance workflow including tests, code polishing, review, and commit. Use when the user asks to "finalize implementation", "finalize changes", "wrap up implementation", "finish up", "ready to commit", or "run QA workflow".
331SKILL.mdUpdated May 9, 2026
tobihagemann/understand-change
tools
VerifiedTrustedCommunity
Teach the user to deeply understand a change through interactive tutoring: restating understanding, drilling into why/what/how, and quizzing until mastery. The active counterpart to a one-shot explanation. Use when the user asks to "understand this change", "teach me this change", "help me understand what changed", "walk me through this change", "make sure I understand this", "quiz me on this", or "teach me what we did".
319SKILL.mdUpdated Jun 4, 2026