Agent skill

Commit Trailers

by vibeeval in vibeeval/vibecosystem

Commit mesajlarina yapilandirilmis karar trailer'lari ekle. An agent skill from vibeeval/vibecosystem.

MITAuto-check passed

Install Commit Trailers

skills CLI
$ npx skills add vibeeval/vibecosystem --skill commit-trailers -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install vibeeval/vibecosystem commit-trailers --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/vibeeval/vibecosystem.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/commit-trailers .claude/skills/commit-trailers && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
commit-trailers
GitHub stars
531
Token cost
~1.3k tokens
SKILL.md length
388 words
Files
1
Skills in repo
144
Repo updated
First seen
Licence
MIT

At a glance

Commit mesajlarina yapilandirilmis karar trailer'lari ekle. An agent skill from vibeeval/vibecosystem.

  • SKILL.md covers Standard Trailers, When to Use Each Trailer, Trailer Reference and Full Example, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Commit Trailers is an agent skill from vibeeval/vibecosystem. Commit mesajlarina yapilandirilmis karar trailer'lari ekle. Constraint, Rejected, Confidence, Scope-risk, Not-tested trailer'lari ile karar baglamini koru.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: AI software team for Claude Code - 138 agents, 295 skills, 73 hooks. Self-learning, multi-agent swarm, autonomous skill evolution. The licence is MIT.

Example prompts

  • “/commit-trailers”

What it can do on your machine

Read from SKILL.md and the folder at commit 3b763b1. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Commit Trailers loads about 1.3k tokens when it runs. Until then it costs about 43 tokens; SKILL.md has 388 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~43
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from vibeeval/vibecosystem at commit 3b763b1, republished under its MIT licence (© vibeeval). 388 words, ~1,295 tokens.

Download SKILL.mdSave it as .claude/skills/commit-trailers/SKILL.md (or your agent's skills folder).
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

TrailerWhen to IncludeWhen to Skip
ConstraintExternal limitation forced a non-obvious decisionNo external constraints applied
RejectedA reasonable alternative was considered and discardedOnly one approach was viable
ConfidenceCorrectness is uncertain or untested in key areasStraightforward well-tested change
Scope-riskChange touches shared infrastructure, middleware, auth, or core data pathsIsolated, single-purpose change
Not-testedA gap in test coverage is intentional and knownAll 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
Show full SKILL.md (161 more words)Show less
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

© vibeeval, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/commit-trailers of vibeeval/vibecosystem.

Open the folder on GitHubat commit 3b763b1

Compare with similar skills

Commit Trailers next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Commit Trailers compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Commit Trailers this skillvibeeval/vibecosystem531—~1.3kAutomated safety check: PassMIT
Commitsickn33/agentic-awesome-skills47k2 repos~1.3kAutomated safety check: PassMIT
Commitdavila7/claude-code-templates32k3 repos~730Automated safety check: PassMIT
Commitwindmill-labs/windmill18k—~447Automated safety check: PassCustom licence
Commitccusage/ccusage19k—~722Automated safety check: PassCustom licence
Commitantiwork/gumroad9.8k—~503Automated safety check: PassMIT

Similar skills

  • Commit

    sickn33/agentic-awesome-skills

    ALWAYS use this skill when committing code changes — never commit directly without it.

    47k GitHub starsUsed in 2 repos~1.3k tokens
    DevelopmentAuto-check passed
  • Commit

    davila7/claude-code-templates

    Create commit messages following Sentry conventions. An agent skill from davila7/claude-code-templates.

    32k GitHub starsUsed in 3 repos~730 tokens
    DevelopmentAuto-check passed
  • Commit

    windmill-labs/windmill

    Create a git commit with conventional commit format. An agent skill from windmill-labs/windmill.

    18k GitHub stars~447 tokensUpdated today
    DevelopmentAuto-check passed
  • Commit

    ccusage/ccusage

    Creates atomic Conventional Commits. An agent skill from ccusage/ccusage.

    19k GitHub stars~722 tokensUpdated today
    DevelopmentAuto-check passed
  • Commit

    antiwork/gumroad

    Stage and commit changes with a clear, concise commit message.

    9.8k GitHub stars~503 tokensUpdated today
    DevelopmentAuto-check passed
  • Commits

    redis/RedisInsight

    Official

    Generate commit messages following Conventional Commits format.

    8.9k GitHub stars~451 tokensUpdated 2 days ago
    DevelopmentAuto-check passed

More from vibeeval/vibecosystem

All 144 skills in this repo
  • Agent Benchmark

    vibeeval/vibecosystem

    Framework for measuring and tracking agent response quality over time.

    531 GitHub stars~2.9k tokensUpdated 1 mo ago
    Auto-check passed
  • Differential Review

    vibeeval/vibecosystem

    Security-focused differential code review with blast radius analysis, risk-adaptive depth (DEEP/FOCUSED/SURGICAL), git history correlation, and structured finding format.

    531 GitHub stars~1.6k tokensUpdated 1 mo ago
    Auto-check passed
  • Factcheck Guard

    vibeeval/vibecosystem

    A skill your agent uses when making any factual claim about the codebase — existence, absence, or behavior.

    531 GitHub stars~2.2k tokensUpdated 1 mo ago
    Auto-check passed
  • Fp Check

    vibeeval/vibecosystem

    Systematic false positive verification for security findings.

    531 GitHub stars~1.6k tokensUpdated 1 mo ago
    Auto-check passed
  • N8n Workflows

    vibeeval/vibecosystem

    n8n otomasyon workflow'lari. An agent skill from vibeeval/vibecosystem.

    531 GitHub stars~3.3k tokensUpdated 1 mo ago
    Auto-check passed
  • Notepad System

    vibeeval/vibecosystem

    A skill your agent uses when context compression is imminent, when resuming a session, or when preserving critical decisions across long tasks.

    531 GitHub stars~1.7k tokensUpdated 1 mo ago
    Auto-check passed

Questions about Commit Trailers

What does Commit Trailers do?

Commit mesajlarina yapilandirilmis karar trailer'lari ekle. An agent skill from vibeeval/vibecosystem. Commit Trailers is an agent skill from vibeeval/vibecosystem. Commit mesajlarina yapilandirilmis karar trailer'lari ekle.

How do I install Commit Trailers in Claude Code?

Run `npx skills add vibeeval/vibecosystem --skill commit-trailers -a claude-code`. Or copy the skill folder (skills/commit-trailers in vibeeval/vibecosystem) into .claude/skills/commit-trailers in your project. Claude Code loads it when a task matches its description.

How do I install Commit Trailers in Codex?

Run `npx skills add vibeeval/vibecosystem --skill commit-trailers -a codex`. Or copy the skill folder (skills/commit-trailers in vibeeval/vibecosystem) into .agents/skills/commit-trailers in your project. Codex loads it when a task matches its description.

Can I use Commit Trailers in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add vibeeval/vibecosystem --skill commit-trailers -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/commit-trailers, .gemini/skills/commit-trailers, .github/skills/commit-trailers and .opencode/skills/commit-trailers in your project.

What does Commit Trailers need to run?

SKILL.md names no scripts, command-line tools or credentials: Commit Trailers is instructions for the agent only.

Does Commit Trailers access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Commit Trailers safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Commit Trailers use?

Commit Trailers is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Commit Trailers use?

About 1.3k tokens (SKILL.md is roughly 5.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Commit Trailers?

Skills that share tags, products or a category with Commit Trailers: Commit (sickn33/agentic-awesome-skills, 47k stars), Commit (davila7/claude-code-templates, 32k stars), Commit (windmill-labs/windmill, 18k stars) and Commit (ccusage/ccusage, 19k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Commit Trailers?

vibeeval (a GitHub user) maintains it in vibeeval/vibecosystem, which has 531 GitHub stars. The repository holds 144 skills in this directory. The repository was last updated on August 8, 2026.

Source: vibeeval/vibecosystem on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.