commit-categories
Commit categorization rules for changelogs and "what's new" summaries. MUST be loaded before categorizing commits in changelog or whats-new commands. Provides the canonical path-based category table used to group commits by area.
- Installs
- 45
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/cloudflare/workerd --skill commit-categories- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads commit-categories automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Commit Categories
Categorize commits by the files they touch, using the primary area for commits spanning multiple categories.
| Category | Path patterns |
|---|---|
| API | src/workerd/api/ (excluding node/ and pyodide/) |
| Node.js compat | src/workerd/api/node/, src/node/ |
| Python | src/workerd/api/pyodide/, src/pyodide/ |
| Rust | src/rust/ |
| Cloudflare APIs | src/cloudflare/ |
| I/O | src/workerd/io/ |
| JSG | src/workerd/jsg/ |
| Server | src/workerd/server/ |
| Build | build/, MODULE.bazel, BUILD.bazel |
| Types | types/ |
| Docs / Config | Documentation, agent/tool configs, .md files |
| Tests | Changes exclusively in test files |
| Other | Anything that doesn't fit above |
Cross-cutting callouts
These are not primary categories — they are additional callout sections that appear alongside the main categories whenever a commit touches the relevant files. A single commit can appear in both a primary category and one or more callouts.
| Callout | Trigger |
|---|---|
| New/Updated Compat Flags | Changes to src/workerd/io/compatibility-date.capnp or new compatibilityFlags references in code |
| New/Updated Autogates | Changes to src/workerd/io/supported-autogates.h or new autogate registrations |
When either callout applies, add a dedicated section after the main categories listing each new or modified flag/gate with a brief description. These must never be buried inside a general category bullet — they are high-visibility items that reviewers and release-note readers need to spot immediately.
How to categorize
- For each commit, run
git diff-tree --no-commit-id --name-only -r <hash>to list files changed. - Match changed files against the path patterns above.
- Assign the commit to whichever category covers the majority of its changes.
- For commits touching multiple areas, list under the primary area (the one with the most changed files or the most significant change).
- Check every commit against the cross-cutting callout triggers. If a commit adds or modifies compat flags or autogates, note it in the corresponding callout section in addition to its primary category.
- Omit empty categories and unused callout sections from output.
FAQ
What does the commit-categories skill do?
Commit categorization rules for changelogs and "what's new" summaries. MUST be loaded before categorizing commits in changelog or whats-new commands. Provides the canonical path-based category table used to group commits by area.
How do I install commit-categories?
Run npx skills add https://github.com/cloudflare/workerd --skill commit-categories in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/commit-categories/ (personal) or .claude/skills/commit-categories/ (project).
Which AI agents can use commit-categories?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is commit-categories safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains commit-categories?
It is published by cloudflare in cloudflare/workerd, and it is an official skill from the maker of the technology it covers. It has 45 recorded installs.
More from cloudflare/workerd
verification-before-completion
cloudflare/workerd
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
rust-review
cloudflare/workerd
Open the skill to read its SKILL.md instructions.
dad-jokes
cloudflare/workerd
After completing any task that took more than 5 tool calls, or after long-running builds/tests finish, load this skill and deliver a dad joke to lighten the mood. Also load before any user-requested joke, pun, or limerick. Never improvise jokes without loading this skill first.
markdown-drafts
cloudflare/workerd
Use markdown formatting when drafting content intended for external systems (GitHub issues/PRs, Jira tickets, wiki pages, design docs, etc.) so formatting is preserved when the user copies it. Load this skill before producing any draft the user will paste elsewhere.
receiving-code-review
cloudflare/workerd
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
workerd-api-review
cloudflare/workerd
Performance optimization, API design & compatibility, security vulnerabilities, and standards spec compliance for workerd code review. Covers tcmalloc-aware perf analysis, compat flags, autogates, web standards adherence, and security patterns. Load this skill when reviewing API changes, performance-sensitive code, security-relevant code, or standards implementations.
Popular code quality & workflow skills
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
improve-codebase-architecture
mattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
handoff
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
domain-modeling
mattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
codebase-design
mattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.