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.
Install
git clone https://github.com/cloudflare/workerd /tmp/workerd && ln -s /tmp/workerd/.opencode/skills/commit-categories ~/.claude/skills/commit-categoriesFrom README
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.
More from this repo
bazel-test-hygiene
Mandatory rules for running bazel tests during development.
dad-jokes
After completing any task that took more than ~5 tool calls, or after long-running builds/tests finish, load this skill...
find-and-run-tests
How to find, build, and run tests in workerd.