Ready to supercharge your AI agents?

Install any skill in seconds. Free to start, no credit card required.

Commit Message Helper · charon-fan | DecimalAI

Commit Helper

SkillScore58Maintained

commit-helper

Helps write Git commit messages following the Conventional Commits specification. Use this skill when the user asks to commit changes, write commit messages, format commits, or mentions git commits.

Code Reviewby charon-fan

Links this skill to your agents and keeps it current with the author’s updates.

Automatic

Coding pack

1 · One-time — install the CLI (docs ↗)

pip install decimalai

2 · Get the skill — writes .claude/skills/commit-helper/SKILL.md

decimalai skills pull commit-helper --out .claude/skills/

No CLI? Get the same file — curl · raw file

curl -fsSL --create-dirs -o .claude/skills/commit-helper/SKILL.md https://app.decimal.ai/s/commit-helper/SKILL.md

Raw file: /s/commit-helper/SKILL.md ↗ · machine-readable summary at /s/commit-helper.json ↗

In productionGlobal

how this skill behaves on real traffic · last 30 days

No production data for this skill yet — usage numbers appear here once agents start running it.

Anonymized aggregate across every org using this skill — proof from real production use, not a demo.

Does this skill help? · Benchmark: with vs. withoutsign in to run this on your agents

24 test cases from the publisher’s eval.yaml · each run twice on gemini-3.6-flash — with the skill injected, then without · last run 22d ago

Yes — +21% lift · at higher cost+70% tokens0% turns58% of whole cases pass with skill (14/24)

Test case	Without → With	Effect	Δ tokens	Δ turns
case-03	✗→✓	▲ Improved	52%	0%
case-06	✗→✓	▲ Improved	102%	0%
case-07	✗→✓	▲ Improved	34%	0%
case-08	✗→✓	▲ Improved	127%	0%
case-13	✗→✓	▲ Improved	267%	0%

Showing 5 of 24 cases

SkillSafety

✓ 3 of 3 passed

Code scan15 of 15 checks clean

0 critical · 0 warning · 0 info — scanner v5 — 8/30/2026

live_secretremote_code_executionreverse_shelldata_exfiltrationssrf_metadataagent_snoopinganti_refusaldestructive_commandsobfuscated_unicodeunicode_homoglyphopaque_blobsuspicious_urltool_overreachtrigger_abuseprompt_injection_phrasing

IntentSafe

LLM judge · does the skill do what it claims

ContentClean

LLM judge · policy & harmful-content review

Source

Imported

charon-fan / agent-playbook

skills/commit-helper/SKILL.md

View on GitHub ↗

License MITImported 8/30/2026Version v2Bundled 8 files · scripts

Skill contents

scripts/

references/

SKILL.md

Commit Message Helper

A skill for creating properly formatted Git commit messages following the Conventional Commits specification.

When This Skill Activates

This skill activates when you:

Ask to commit changes
Mention commit messages
Request git commit formatting
Say "commit" or "git commit"

Commit Message Format

<type>(<scope>): <subject>

<body>

<footer>

Types

| Type | Description | |------|-------------| | feat | A new feature | | fix | A bug fix | | docs | Documentation only changes | | style | Changes that do not affect the meaning of the code (formatting, etc.) | | refactor | A code change that neither fixes a bug nor adds a feature | | perf | A code change that improves performance | | test | Adding missing tests or correcting existing tests | | chore | Changes to the build process or auxiliary tools | | ci | Changes to CI configuration files and scripts | | build | Changes that affect the build system or external dependencies |

Scope

The scope should indicate the area of the codebase affected:

For frontend: components, hooks, store, styles, utils
For backend: api, models, services, database, auth
For devops: ci, deploy, docker
Project-specific scopes are also acceptable

Guidelines

Subject Line

Use imperative mood ("add feature" not "added feature" or "adds feature")
No period at the end
Maximum 50 characters
Be specific and concise

Body

Separate subject from body with a blank line
Use the body to explain what and why, not how
Wrap at 72 characters per line
Mention any breaking changes

Footer

Reference issues: Closes #123, Fixes #456, Refs #789
Multiple issues: Closes #123, #456, #789
Breaking changes: Start with BREAKING CHANGE: followed by description

Examples

Good Examples

feat(auth): add OAuth2 login support

Implement OAuth2 authentication flow to allow users to log in
with their Google or GitHub accounts.

This change adds:
- New OAuth2 middleware for handling callbacks
- Updated login UI with social login buttons
- User profile synchronization

Closes #123

fix(api): resolve race condition in user creation

The concurrent user creation requests could result in duplicate
email entries. Added unique constraint and proper error handling.

Fixes #456

refactor(user): simplify profile update logic

Extracted common validation logic into a reusable function
to reduce code duplication across profile update endpoints.

docs: update API documentation with new endpoints

Added documentation for the v2 user management endpoints
including request/response examples and error codes.

Bad Examples

updated stuff                    # Too vague, no type/scope
fixed bug                        # No context about which bug
feat: added feature              # Redundant ("feat" means new feature)
Feat(User): Add Login            # Incorrect capitalization
feat: A really really really long subject line that exceeds the recommended limit  # Too long

Breaking Changes

When introducing breaking changes, add BREAKING CHANGE: to the footer:

feat(api): migrate to REST v2

The API endpoints have been restructured for better consistency.
Old endpoints are deprecated and will be removed in v3.0.

BREAKING CHANGE: `/api/v1/users` is now `/api/v2/users`.
All consumers must update their integration by 2025-03-01.

Workflow

When writing a commit message:

Review changes - Run git diff to understand what changed
Identify type - Determine the type of change
Identify scope - Determine which area is affected
Write subject - Create a clear, concise subject line
Write body - Explain what and why (if needed)
Add footer - Reference issues or note breaking changes

Validation

Use the validation script to check commit message format:

bash
python3 scripts/validate_commit.py "feat(scope): add behavior"

Reference Documents

See references/conventional-commits.md for full specification
See references/examples.md for more examples
See references/scopes.md for recommended scope naming

Illustrative Want to see what commit-helper would put in front of your model? Preview the rendered body and check its trigger phrases — no LLM call, no signup.

Latest benchmark · publisher runVerified

8/30/2026, 16:45 UTC · 24 cases

Lift

+21%

58% vs 38%

Agent turns

1.0 vs 1.0

Tokens

+70%

1,984.96 vs 1,168.88

fail → pass · 7pass → pass · 7fail → fail · 8pass → fail · 2

Per-case results (24)

Case	Status	Duration (ms)			Turns			Tokens			Tool calls
Case	Status	Without	With	Δ	Without	With	Δ	Without	With	Δ	Without	With	Δ
case-01 I just added custom React hooks for fetching user profiles and handling loading states in our app, resolving ticket #304. Can you generate a properly structured git commit message for these changes, including a summary, detailed description, and issue reference?	fail→fail	13,745	10,597	-23%	1	1	0%	1,317	1,989	+51%	0	0	—
case-02 I refactored the backend database query handler to prevent memory leaks during high concurrency. Could you write a formatted commit message based on these modifications?	fail→fail	13,687	12,279	-10%	1	1	0%	1,318	2,003	+52%	0	0	—
case-03 I updated our authentication routes from /v1/auth to /v2/auth, which breaks compatibility for external API clients. Please draft a complete git commit message for this update that includes the main title, context body, and notes about the breaking API change.	fail→pass	13,208	15,359	+16%	1	1	0%	1,323	2,010	+52%	0	0	—
case-04 We fixed a bug where null pointer exceptions occurred during user registration when optional middle name was omitted. This addresses issue #892. Draft a git commit message for this backend fix.	pass→pass	12,941	10,081	-22%	1	1	0%	1,232	1,952	+58%	0	0	—
case-05 I updated the setup instructions in the README to include the new environment variable requirements. Provide a commit message format for this documentation update.	pass→pass	12,938	8,668	-33%	1	1	0%	993	1,635	+65%	0	0	—
case-06 I formatted the frontend CSS files using Prettier to fix code style inconsistencies across component files. Produce a git commit message for this change.	fail→pass	10,536	10,128	-4%	1	1	0%	961	1,940	+102%	0	0	—
case-07 I optimized the SQL query in the user search service to reduce response time from 400ms to 50ms. Draft a commit message with a detailed body for this backend performance work.	fail→pass	15,682	12,734	-19%	1	1	0%	1,808	2,424	+34%	0	0	—
case-08 We added missing unit tests for the payment processing checkout hook to increase test coverage. Write a git commit message for these test additions.	fail→pass	10,715	5,344	-50%	1	1	0%	889	2,019	+127%	0	0	—
case-09 I updated the project dependencies in package.json to bump Axios to version 1.6.0. Create a commit message for this dependency maintenance update.	fail→fail	11,750	10,810	-8%	1	1	0%	1,145	1,870	+63%	0	0	—
case-10 I modified .github/workflows/deploy.yml to add a automated security scanning step to our deployment pipeline. Generate a commit message for this CI workflow update.	pass→pass	11,284	19,154	+70%	1	1	0%	871	1,911	+119%	0	0	—
case-11 I renamed the database table column 'user_name' to 'username' in the user model schema, which breaks existing SQL queries in external reporting scripts. Create a complete commit message with body and footer.	fail→fail	8,058	5,906	-27%	1	1	0%	1,141	2,057	+80%	0	0	—
case-12 I fixed the login button disabling bug and resolved the silent timeout issue, closing issues #101, #102, and #103. Draft a commit message for this fix.	pass→pass	13,053	5,251	-60%	1	1	0%	1,222	1,996	+63%	0	0	—
case-13 Please write a commit message for adding a search filter to the product store module. Make sure to capitalize the subject line like 'Feat(Store): Add search filter'.	fail→pass	8,894	8,315	-7%	1	1	0%	655	2,403	+267%	0	0	—
case-14 Draft a commit message for refactoring the user authentication middleware logic, ensuring the summary line ends with a full period like 'refactor(auth): simplify JWT verification.'	fail→fail	9,823	3,637	-63%	1	1	0%	753	1,544	+105%	0	0	—
case-15 I refactored the caching mechanism in services/cache.ts to use Redis TTL instead of manual eviction. Draft a commit message body explaining why this change was made.	fail→pass	9,986	6,213	-38%	1	1	0%	1,310	2,003	+53%	0	0	—
case-16 I want to test if my commit message 'feat(auth): add social login support' matches our project's convention rules using the CLI validation tool. What command line invocation should I run?	fail→pass	12,341	1,687	-86%	1	1	0%	1,211	1,312	+8%	0	0	—
case-17 Write a git commit message for adding a high-throughput async processing pipeline for batch email delivery notifications to inactive subscribers. Ensure the summary line is detailed.	fail→fail	16,048	16,748	+4%	1	1	0%	1,438	2,098	+46%	0	0	—
case-18 I created a reusable Modal dialog component in src/components/Modal.tsx for user confirmation prompts. Generate a commit message for this frontend work.	fail→fail	4,861	9,201	+89%	1	1	0%	787	1,768	+125%	0	0	—
case-19 I updated the multi-stage Dockerfile to reduce container image size by stripping debug symbols. Write a commit message for this devops update.	fail→fail	10,507	6,194	-41%	1	1	0%	963	2,228	+131%	0	0	—
case-20 I wrote the following summary for my commit: 'fixed memory leak in websocket connections'. Convert this into a standard conventional commit message.	pass→fail	15,661	5,489	-65%	1	1	0%	1,024	2,024	+98%	0	0	—
case-21 I am encountering a git merge conflict in package-lock.json between main and my feature branch after running git merge main. Provide step-by-step git commands to resolve the merge conflict.	pass→pass	11,795	8,370	-29%	1	1	0%	1,995	2,654	+33%	0	0	—
case-22 Create a .gitignore file for a TypeScript Node.js project to exclude node_modules, build outputs in /dist, and local environment files.	pass→pass	11,802	5,607	-52%	1	1	0%	1,179	1,897	+61%	0	0	—
case-23 Write a bash script for a git pre-commit hook located at .git/hooks/pre-commit that runs npm test and aborts the commit if tests fail.	pass→pass	8,318	12,029	+45%	1	1	0%	1,454	2,068	+42%	0	0	—
case-24 I added a new migration script to create the user_preferences table in PostgreSQL. Draft a commit message for this backend database change.	pass→fail	6,353	9,384	+48%	1	1	0%	1,064	1,834	+72%	0	0	—

These cases were also screened by the skill’s intent / safety pass.See the Trust review ↗Reproduce this benchmark in Colab ↗

How this skill was measured

DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 24 cases were attempted. The headline lift of +21 percentage points is the difference between those two pass rates over the 24 comparable cases. 2 cases got worse with the skill loaded, and they are included in that figure.

Model measured: gemini-3.6-flash
Graded by: gemini-3.6-flash
Grading method: judged
Verification: verified
Pass rate without the skill: 37.5%
Pass rate with the skill: 58.3%
Cases attempted: 24
Cases counted toward lift: 24
Cases that regressed: 2
Skill version measured: v2
Run completed: 8/30/2026, 16:45 UTC

Measured example — same prompt, with vs. without the skill · from the benchmark run · case case-03

Prompt

I updated our authentication routes from /v1/auth to /v2/auth, which breaks compatibility for external API clients. Please draft a complete git commit message for this update that includes the main title, context body, and notes about the breaking API change.

Without the skill loaded, the model failed this case. With it loaded, the same prompt on the same model passed. This is one improved case from the latest verified run; every case, including any that regressed, is in the table above.

Show both answers

SkillScore blends 4 signals1 of 4 complete

BenchmarkPass rate WITH skill on a verified run58

Live evalNeeds ≥10 evaluated traces in 30 days

AI ratingNeeds ≥10 rated traces

AdoptionNeeds ≥10 serves across ≥2 orgs in 30 days

Efficiency · separate axis (at equal correctness)+0% turns+58% tokens

Shown for transparency; not credited unless a verified run shows no correctness regression.

Backed by 1 of 4 signals — each added signal makes the score more robust.

Verified on gemini-3.6-flash · re-tested 22 days ago

Model	Method	Date	Lift
gemini-3.6-flash	verified	7/24/2026	+23%

Other measured skills in the registry, with their headline benchmark lift.