SkillAgentSearch skills...

commit-trailers

Commit mesajlarina yapilandirilmis karar trailer'lari ekle. Constraint, Rejected, Confidence, Scope-risk, Not-tested trailer'lari ile karar baglamini koru.

Install / Use

npx skills add vibeeval/vibecosystem --skill commit-trailers

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

83/100

Supported Platforms

Universal

Our assessment of commit-trailers

commit-trailers scores 83/100 on our quality scale, 3208th of 4,706 Development & Engineering skills we index.

Its SKILL.md is 5.1 KB long, well organised into 12 sections with 7 code examples: a solid amount of guidance for an agent.

It has 535 GitHub stars, a meaningful sign that others use it.

Substance
26/30
Structure
20/20
Description
15/15
Adoption
12/20
Freshness
11/15

Maintenance, license and trust

  • The repository was last updated about 3 months ago. That is recent enough to be usable, but agent tooling moves fast, so check the instructions against your agent's current version.
  • Our last check on 2026-11-07 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 98/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-04. Automated pattern scan on 2026-10-04. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

commit-trailers compared with similar skills

All 4 of these similar skills score higher than commit-trailers; compare them before choosing.

SkillScoreStarsUpdatedFormat
commit-trailers (this skill)by vibeeval835353mo agoSKILL.md
taste-skillby Leonxlnx100117.6k9d agoCLAUDE.md
Agent-Reachby Panniantong100112.7k10d agoCLAUDE.md
headroomby headroomlabs-ai10079.9ktodayCLAUDE.md
ai-job-searchby ai-job-search-dev10072.3ktodayCLAUDE.md

Frequently asked questions

How do I install commit-trailers?
Run npx skills add vibeeval/vibecosystem --skill commit-trailers. The install tabs above show the steps for each supported agent.
Which AI agents does commit-trailers work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is commit-trailers safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 98/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is commit-trailers still maintained?
The repository was last updated about 3 months ago. That is recent enough to be usable, but agent tooling moves fast, so check the instructions against your agent's current version.

name: commit-trailers description: Commit mesajlarina yapilandirilmis karar trailer'lari ekle. Constraint, Rejected, Confidence, Scope-risk, Not-tested trailer'lari ile karar baglamini koru.

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, middleware, auth, or core data paths | Isolated, single-purpose change | | Not-tested | A gap in test coverage is intentional and known | All paths are tested |

Not every commit needs trailers. A fix: typo in error message needs none. A new auth middleware affecting every API call needs all five.


Trailer Reference

Constraint

An external limitation — browser API, hosting restriction, library limitation, business rule, or environment constraint — that ruled out the obvious solution.

Constraint: Safari 15 does not support the CSS :has() selector
Constraint: Redis unavailable in staging — in-memory fallback only
Constraint: Must stay on Node 18, no upgrade path in scope
Constraint: Third-party payment API does not support idempotency keys

Rejected

An alternative that was seriously considered. Helps future maintainers understand why the current approach exists instead of the simpler-looking one they are thinking of.

Rejected: Redux — too much boilerplate for this feature's scope
Rejected: JWT stored in localStorage — XSS exposure, using httpOnly cookie instead
Rejected: Direct DB query — bypasses cache layer, use repository instead
Rejected: Polling every 5s — too much server load, went with SSE instead

Confidence

Signal the quality of certainty around the correctness of the change. low should trigger a code review comment or discussion before merge.

Confidence: high
Confidence: medium — edge case with concurrent writes not covered by tests
Confidence: low — reversing this migration is complex, needs review before merge

Scope-risk

Signal how much of the system this change can affect if it is wrong. Helps reviewers and the team calibrate how carefully to review and test.

Scope-risk: low
Scope-risk: medium — touches payment processing, needs manual smoke test
Scope-risk: high — auth middleware change, every authenticated endpoint affected

Not-tested

Explicitly acknowledge a test gap. This is honest engineering, not an excuse. A named gap is better than an invisible one.

Not-tested: email delivery — no SMTP server in test environment
Not-tested: concurrent request behavior — requires load testing setup
Not-tested: Safari-specific rendering — no CI browser suite yet
Not-tested: DB rollback on payment failure — requires Stripe test mode setup

Full Example

feat: add rate limiting to API endpoints

Implement token bucket algorithm for /api/* routes.
Limits: 100 requests/min for free tier, 1000 for paid tier.
Exceeding the limit returns 429 with Retry-After header.

Constraint: Redis required for distributed rate limiting — in-memory does not work across multiple instances
Rejected: express-rate-limit — lacks per-user tier support without significant custom logic
Confidence: high
Scope-risk: medium — affects all /api/* routes, auth and webhook routes excluded
Not-tested: sustained 10K+ req/min behavior — requires dedicated load test environment

Format Rules

  • Trailers go AFTER the commit body, separated by a blank line
  • One trailer per line, no line wrapping
  • Rejected may appear multiple times (one per rejected alternative)
  • Only include trailers that add genuine value — avoid mechanical inclusion
  • Confidence: low is a signal for the team, not a reason to skip the commit
  • This format supplements, not replaces, the conventional commit type prefix

Integration with Other Rules

  • safety-and-quality.md defines the base commit format (<type>: <description>)
  • This rule adds optional trailers on top of that format
  • full-autonomy.md requires commit approval — trailers give Batuhan the context to approve confidently
  • Trailers are the commit-level equivalent of Priority Notes in the notepad system

Related Skills

View on GitHub
GitHub Stars535
CategoryDevelopment
Updated3mo ago
Forks44

Languages

C#

Trust signals

98/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 info