commit-categories
$
npx mdskill add cloudflare/workerd/commit-categoriesDetermine the appropriate functional area for commits to structure changelogs and release notes.
- Groups changes by code path to generate structured 'what's new' sections.
- Requires prior loading before executing changelog or whats-new commands.
- Uses a predefined, path-based mapping to assign a primary category to commits.
- Provides a canonical table of categories and associated file patterns for consumption.
SKILL.md
.github/skills/commit-categoriesView on GitHub ↗
--- name: commit-categories description: 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. --- # 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 1. For each commit, run `git diff-tree --no-commit-id --name-only -r <hash>` to list files changed. 2. Match changed files against the path patterns above. 3. Assign the commit to whichever category covers the majority of its changes. 4. For commits touching multiple areas, list under the **primary** area (the one with the most changed files or the most significant change). 5. 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. 6. Omit empty categories and unused callout sections from output.
More from cloudflare/workerd
- add-autogateStep-by-step guide for adding a new autogate to workerd for gradual rollout of risky changes, including enum registration, string mapping, usage pattern, and testing.
- add-compat-flagStep-by-step guide for adding a new compatibility flag to workerd, including capnp schema, C++ usage, testing, and documentation requirements.
- bazel-test-hygieneMandatory rules for running bazel tests during development. Load this skill before running any bazel test command, especially when validating fixes or verifying regression tests. Prevents false confidence from cached results, filter flags that silently match nothing, and partial test runs that miss breakage.
- dad-jokesAfter 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.
- find-and-run-testsHow to find, build, and run tests in workerd. Covers wd-test, kj_test target naming, bazel query patterns, and common flags. Also covers parent project integration tests if workerd is used as a submodule. Load this skill when you need to locate or run a test and aren't sure of the exact target name or invocation.
- identify-reviewerIdentifies the local user's GitHub account and git identity before performing code reviews. Load this skill at the start of any PR review, code review, or commit log analysis so findings can be framed relative to the user's own prior comments, commits, and approval status.
- investigation-notesStructured scratch tracking document for investigation state during bug hunts - prevents re-reading code, losing context, and rabbit holes; maintains external memory so you don't re-derive conclusions
- kj-styleKJ/workerd C++ style guidelines for code review. Covers naming, type usage, memory management, error handling, inheritance, constness, and formatting conventions. Load this skill when reviewing or writing C++ code in the workerd codebase.
- markdown-draftsUse 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.
- module-registryLoad when working with the module registry in workerd — reading, modifying, debugging, or reviewing module resolution, compilation, evaluation, or registration code. Provides pointers to three reference documents covering the legacy registry, V8 module internals, and the new registry design.