Git Commit
- 59 installs
- 1.1k repo stars
- Updated August 4, 2026
- cloudflare/sandbox-sdk
git-commit is an agent skill that enforces concise imperative git commit messages following seven project standards rules.
About
The git-commit skill ensures commit messages follow project standards using seven rules for great commit messages focused on conciseness and imperative mood. Rules require separating subject from body with a blank line, limiting the subject to fifty characters, capitalizing without a trailing period, using imperative mood like Add feature not Added feature, wrapping body text at seventy-two characters, and explaining what and why rather than how. Key principles emphasize concise value per word, subjects that stand alone without requiring the body, focusing on the change rather than review feedback, and avoiding bullet points in bodies. Format guidance mandates HEREDOC usage for proper multi-line commits via git commit -m with cat EOF wrappers. Good examples show short standalone subjects or brief bodies explaining encoding bugs, while bad examples illustrate vague subjects and over-explained implementation details. A pre-commit checklist verifies subject length, imperative mood, capitalization, no review references, no bullet bodies, and no sensitive files like .env or credentials.
- Enforces seven rules for concise imperative commit messages.
- Limits subject lines to fifty characters without trailing periods.
- Requires HEREDOC formatting for multi-line commit bodies.
- Discourages review feedback references and bullet-point bodies.
- Includes pre-commit checklist for subject style and sensitive files.
Git Commit by the numbers
- 59 all-time installs (skills.sh)
- Ranked #277 of 733 Git & Pull Requests skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
git-commit capabilities & compatibility
- Capabilities
- seven rule commit message standard enforcement · heredoc multi line commit formatting · good and bad commit example guidance · pre commit checklist for style and secrets
- Works with
- github · gitlab · bitbucket
- Use cases
- code review
What git-commit says it does
Limit the subject line to 50 characters
Focus on the change, not how it was discovered
npx skills add https://github.com/cloudflare/sandbox-sdk --skill git-commitAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 59 |
|---|---|
| repo stars | ★ 1.1k |
| Last updated | August 4, 2026 |
| Repository | cloudflare/sandbox-sdk ↗ |
How do I write git commit messages that follow project standards with clear subjects and bodies?
Create git commits that follow project standards with concise imperative subjects and optional explanatory bodies.
Who is it for?
Contributors creating git commits who need enforced subject length, imperative mood, and HEREDOC formatting.
Skip if: Skip for non-git workflows or repositories with unrelated commit message conventions not covered here.
When should I use this skill?
User asks to create a git commit and needs messages following project commit standards.
What you get
A properly formatted commit with imperative subject, optional why-focused body, and no sensitive files included.
Files
Git Commit Guidelines
Follow these rules when creating commits for this repository.
The 7 Rules
1. Separate subject from body with a blank line 2. Limit the subject line to 50 characters 3. Capitalize the subject line 4. Do not end the subject line with a period 5. Use the imperative mood ("Add feature" not "Added feature") 6. Wrap the body at 72 characters 7. Use the body to explain what and why vs. how
Key Principles
Be concise, not verbose. Every word should add value. Avoid unnecessary details about implementation mechanics - focus on what changed and why it matters.
Subject line should stand alone - don't require reading the body to understand the change. Body is optional and only needed for non-obvious context.
Focus on the change, not how it was discovered - never reference "review feedback", "PR comments", or "code review" in commit messages. Describe what the change does and why, not that someone asked for it.
Avoid bullet points - write prose, not lists. If you need bullets to explain a change, you're either committing too much at once or over-explaining implementation details.
Format
Always use a HEREDOC to ensure proper formatting:
git commit -m "$(cat <<'EOF'
Subject line here
Optional body paragraph explaining what and why.
EOF
)"Good Examples
Add session isolation for concurrent executionsFix encoding parameter handling in file operations
The encoding parameter wasn't properly passed through the validation
layer, causing base64 content to be treated as UTF-8.Bad Examples
Update files
Changes some things related to sessions and also fixes a bug.Problem: Vague subject, doesn't explain what changed
Add file operations support
Implements FileClient with read/write methods and adds FileService
in the container with a validation layer. Includes comprehensive test
coverage for edge cases and supports both UTF-8 text and base64 binary
encodings. Uses proper error handling with custom error types from the
shared package for consistency across the SDK.Problem: Over-explains implementation details, uses too many words
Checklist Before Committing
- [ ] Subject is ≤50 characters
- [ ] Subject uses imperative mood
- [ ] Subject is capitalized, no period at end
- [ ] Body (if present) explains why, not how
- [ ] No references to review feedback or PR comments
- [ ] No bullet points in body
- [ ] Not committing sensitive files (.env, credentials)
Related skills
Caveman CommitGenerate terse, Conventional Commits messages that preserve intent without fluff or AI attribution.272k94k
Resolving Merge ConflictsQuickly understand, resolve, and commit merge conflicts without losing work or breaking their flow.183k193kGit Guardrails Claude CodePrevent Claude Code from accidentally running destructive git commands like force push, hard reset, or clean.175k193k
Using Git WorktreesGuarantee every new feature or implementation task runs inside a clean, isolated workspace without polluting the main branch or current working directory.149k263k
Git CommitGenerate accurate conventional commit messages and intelligently stage files directly from natural language requests.40.6k37.2k
Resolve Merge ConflictsQuickly understand and resolve Git merge conflicts without losing context or breaking changes.16.5k148FAQ
What does git-commit produce?
A commit message following seven rules with imperative subject, optional body, and HEREDOC formatting guidance.
When should I use git-commit?
When creating git commits that must follow concise imperative project standards.
Is git-commit safe to install?
Review the Security Audits panel on this page before installing in production.