commit-trailers
Commit mesajlarina yapilandirilmis karar trailer'lari ekle. Constraint, Rejected, Confidence, Scope-risk, Not-tested trailer'lari ile karar baglamini koru.
Profile →npx skills add vibeeval/vibecosystem --skill commit-trailers --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Commit Trailers -- Structured Decision Context Supplement conventional commits with structured trailers that preserve the reasoning behind a change. Future maintainers (and future agents) read commit history to understand not just what changed, but why a specific approach was taken. ## Standard Trailers Add these after the commit body, separated by a blank line, when they add value: ``` Constraint: <external limitation that shaped this approach> Rejected: <alternative considered and the reason it was rejected> Confidence: high | medium | low <how certain we are this is correct> Scope-risk: low | medium | high <blast radius — how much can this break> Not-tested: <what was not tested and why> ``` --- ## When to Use Each Trailer | Trailer | When to Include | When to Skip | |---------|----------------|--------------| | `Constraint` | External limitation forced a non-obvious decision | No external constraints applied | | `Rejected` | A reasonable alternative was considered and discarded | Only one approach was viable | | `Confidence` | Correctness is uncertain or untested in key areas | Straightforward well-tested change | | `Scope-risk` | Change touches shared infrastructure, middlew
- Standard Trailers
- When to Use Each Trailer
- Trailer Reference
- Constraint
- Rejected
- Confidence
- Scope-risk
- Not-tested
- Full Example
- Format Rules
- Integration with Other Rules
What does the commit-trailers skill do?
Commit mesajlarina yapilandirilmis karar trailer'lari ekle. Constraint, Rejected, Confidence, Scope-risk, Not-tested trailer'lari ile karar baglamini koru.
How do I install it?
Run `npx skills add vibeeval/vibecosystem --skill commit-trailers --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From vibeeval/vibecosystem, a repository with 521 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.