trove-commit
Git commit workflow and message conventions. Use when creating, drafting, or reviewing atomic commits with conventional messages.
- License 许可
- MIT
- 所属仓库
- bravew/trove
- 最近更新
- 2026-11-12
- Stars
- ★ 10
- Forks
- 1
01 前言 Front Matter
- name
- trove-commit
- metadata
- { "trove-category": "pull-requests", "trove-category-label": "Pull requests" }
- description
- Git commit workflow and message conventions. Use when creating, drafting, or reviewing atomic commits with conventional messages.
03 SKILL.md 正文
<!-- AUTO-GENERATED from SKILL.md.tmpl — do not edit directly --> <!-- Regenerate: bun run build:skills -->
Session Init
This skill ships Trove conventions. Prefer existing project patterns over generic best practices when they conflict.
Commit Message Conventions
Format
<type>(<scope>): <subject>
<body>
<footer>
Types
| Type | When to Use |
|---|---|
feat |
New feature |
fix |
Bug fix |
refactor |
Code restructuring (no behavior change) |
docs |
Documentation only |
test |
Adding or updating tests |
chore |
Build, deps, config changes |
perf |
Performance improvement |
style |
Code style (formatting, semicolons) |
ci |
CI/CD configuration |
Rules
- Subject line: imperative mood, lowercase, no period, max 72 chars
- Body: explain WHY, not WHAT (the diff shows what changed)
- Scope: optional, identifies the module/area (e.g.,
auth,api,ui) - Breaking changes: add
BREAKING CHANGE:in footer
Stacking and prose
Commit liberally and treat each commit as a future PR: prefer several small, ordered, independently reviewable commits over one fat commit. Rebase them into a clean sequence before opening the PR. Run the message body through trove-unslop (its benefits-from) so it reads as plain prose — explain the why, drop boilerplate.
Direct Commit Workflow
When invoked as an action, create a commit only for a single logical change.
- Inspect
git status --short, recent commits, and the relevant diff. - If paths are provided, limit the review and staging to those paths.
- Stage specific files with
git add <paths>; avoidgit add -Aunless the whole working tree is clearly one change. - Create the commit with the conventional subject and a body when the why is not obvious.
- Report the commit hash, message, and files committed.
If the working tree mixes unrelated changes, stop and name the smaller commit slices. Never include AI-generated or co-author boilerplate.
Examples
feat(auth): add OAuth2 PKCE flow for mobile clients
The implicit grant flow is deprecated by OAuth 2.1. PKCE provides
better security for public clients without a client secret.
Closes #234
fix(api): prevent duplicate webhook processing
Add idempotency check using event ID before processing.
Previously, retried webhooks could create duplicate records.
04 同仓库更多 Skills
using-trove
Skill discipline anchor for the Trove marketplace. Loaded once per session; routes the agent to the right trove-* skill before code, planning, review, or git actions.
trove-write-skill
Skill authoring workflow. Use when creating or updating a Codex or Trove skill, including rubrics, tasks, metadata, and validation.
trove-worktree
Git worktree workflow for spikes, risky experiments, and broad refactors that should not disturb the user's current branch.
trove-why
Reconstruct design rationale and decision history from evidence — source control, issue tracker (Linear), docs (Notion), chat (Slack), error tracking (Sentry) — with calibrated confidence. Use for "why does X work this way", "why did we pick Y", regressions, and postmortems. Use trove-explain for how it works now.
trove-verify
Completion verification workflow. Use before claiming done, fixed, complete, ready, or shipped.
trove-unslop
Cut AI tells from writing — PR descriptions, release notes, specs, commit bodies, and replies. Use before finalizing prose, or when the user asks to clean up, de-slop, or make text sound human.