Ready to supercharge your AI agents?

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

Git Conventions — measured AI agent skill | DecimalAI

fbarrento/git-conventions

SkillScore100Maintained

Canonical naming + message rules for commits, pull request titles, and branch names using Conventional Commits. Defines the shared type vocabulary (feat, fix, refactor, chore, docs, test, perf, build, ci, style, revert), subject grammar, body/footer format, co-author trailer, breaking-change marking, and issue references. Use when writing or reviewing a commit message, naming a PR, or naming a branch. Framework-agnostic — applies to any repo.

by fbarrento

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

Automatic

Coding pack

decimalai skills pull fbarrento-git-conventions

Get this skill — curl · raw file

curl -fsSL https://app.decimal.ai/s/fbarrento-git-conventions/SKILL.md

Raw file: /s/fbarrento-git-conventions/SKILL.md ↗ · machine-readable summary at /s/fbarrento-git-conventions.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 7d ago

Yes — +21% lift+14% tokens0% turns100% of whole cases pass with skill (24/24)

Test case	Without → With	Effect	Δ tokens	Δ turns
case-01	✗→✓	▲ Improved	30%	0%
case-02	✗→✓	▲ Improved	-25%	0%
case-12	✗→✓	▲ Improved	-16%	0%
case-15	✗→✓	▲ Improved	107%	0%
case-19	✗→✓	▲ Improved	28%	0%

Showing 5 of 24 cases

SkillSafety

✓ 3 of 3 passed

Code scan15 of 15 checks clean

0 critical · 0 warning · 0 info — scanner v4 — 8/1/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

fbarrento / laravel-agent-kit

skills/git-conventions/SKILL.md

View on GitHub ↗

Imported 8/1/2026Version v1

Skill contents

SKILL.md

Git Conventions

Canonical home for VCS naming. The new-task skill creates branches; this skill owns the naming rules it (and you) apply. Same type vocabulary spans branch, commit, and PR title.

Type vocabulary (shared by branch / commit / PR)

| Type | Use for | |------|---------| | feat | new user-facing capability | | fix | bug fix | | refactor | behavior-preserving restructuring | | perf | performance improvement | | docs | documentation only | | test | tests only | | chore | maintenance, deps, tooling, workflow | | build | build system / packaging | | ci | CI config / pipelines | | style | formatting only, no logic change | | revert | reverts a prior commit |

Pick the type by intent, not by which files changed.

Commit messages

type(scope): subject

body — what + why, wrapped ~72 cols. optional.

Refs: #123
Co-Authored-By: Name <email>

Rules:

Subject: imperative mood, lowercase start, no trailing period, ≤ ~72 chars.
scope optional, lowercase noun (auth, laravel-rules). type(scope): or bare type:.
Body explains why, not a diff restatement. Blank line after subject.
Issue refs in subject (#1) for the headline issue, or a Refs:/Closes: footer.

Breaking change: add ! before the colon AND a footer.

feat(api)!: drop v1 token endpoint

BREAKING CHANGE: clients must use /v2/tokens.

PR titles

PR title = a Conventional Commit subject. Same grammar, same vocabulary.

Good: feat(quotes): add FinnHub symbol quote service
Good: refactor: restructure laravel-rules into topic folders
Bad: Update stuff, WIP, Fixes.

Squash-merge → the PR title becomes the commit subject, so it must obey the commit rules above.

Branch names

type/kebab-description — same type vocabulary, lowercase kebab-case, short + specific. Creation workflow + guardrails → new-task skill.

Good: fix/waitlist-validation, chore/upgrade-laravel-12.
Bad: patch-1, franciscos-branch.

Checklist

Type chosen by intent from the shared vocabulary.
Commit subject: imperative, lowercase, no period, ≤ ~72.
Body says why (when non-trivial); blank line after subject.
Breaking change marked with ! + BREAKING CHANGE: footer.
Issue referenced ((#1) or footer) when one exists.
PR title obeys commit-subject rules.
Branch is type/kebab-description.

Want to see if fbarrento/git-conventions would activate on your phrasing? Try it before you install — no LLM call, no signup.

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