Loadingβ¦
Use when writing commit messages in a repo with a custom commit format β applies the org's convention ([TICKET] AREA: summary with arbitrary AREA codes) the base won't guess, so commits are consistent and parseable. Template: replace with your format.
| Test case | Without β With | Effect | Ξ tokens | Ξ turns |
|---|---|---|---|---|
| core-errors | Β·βΒ· | β Error | 172% | 0% |
| login-form | Β·βΒ· | β Error | 167% | 0% |
| webhook | Β·βΒ· | β Error | 170% | 0% |
| conn-pool | Β·βΒ· | β Error | 170% | 0% |
| orders-schema | Β·βΒ· | β Error | 169% | 0% |
βThe skill is a benign template that instructs the agent on how to format commit messages according to a specific organizational convention.β
> Template skill. The rules below are a worked example (a fictional "Acme"). Fork this skill and replace them with your organization's real rules β the agent then applies your policy instead of guessing. The measured lift demonstrates the shape works.
Write the commit SUBJECT LINE in OUR exact format: [TICKET] AREA: imperative summary
[TICKET] β the ticket id in SQUARE BRACKETS (given in the input).AREA β our code, mapped from what the change touches: HTTP / network / API client / webhook -> NET;database / SQL / migration / index / connection pool -> DATA; UI / frontend / CSS / styling / page / nav / form -> UI; anything else -> CORE.
This is NOT Conventional Commits β do not use feat:/fix:/chore: etc.