From 4a60ee23b77c942111f3935d325ca5c80424ceb2 Mon Sep 17 00:00:00 2001 From: Trevin Chow Date: Fri, 27 Mar 2026 01:07:58 -0700 Subject: [PATCH] fix: clarify commit prefix selection for markdown product code (#407) Co-authored-by: Claude Opus 4.6 (1M context) --- AGENTS.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/AGENTS.md b/AGENTS.md index 18083af..9c1cee6 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -77,7 +77,7 @@ cat plugins/compound-engineering/.claude-plugin/plugin.json | jq . ## Commit Conventions -- Use conventional titles such as `feat: ...`, `fix: ...`, `docs: ...`, and `refactor: ...`. +- **Prefix is based on intent, not file type.** Use conventional prefixes (`feat:`, `fix:`, `docs:`, `refactor:`, etc.) but classify by what the change does, not the file extension. Files under `plugins/*/skills/`, `plugins/*/agents/`, and `.claude-plugin/` are product code even though they are Markdown or JSON. Reserve `docs:` for files whose sole purpose is documentation (`README.md`, `docs/`, `CHANGELOG.md`). - Component scope is optional. Example: `feat(coding-tutor): add quiz reset`. - Breaking changes must be explicit with `!` or a breaking-change footer so release automation can classify them correctly.