メニュー
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.
SOC 職業分類に基づく
Load 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.
Guidelines for posting pull request review comments via GitHub CLI, including suggested edits format, handling unresolved comments, etiquette, and report/issue tracking. Load this skill when reviewing a PR via GitHub and posting inline comments.
Mandatory 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.
Structured 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
Step-by-step guide for updating the V8 JavaScript engine in workerd, including patch rebasing, dependency updates, integrity hashes, and verification. Load this skill when performing or assisting with a V8 version bump.
KJ/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.
| 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. |
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 |
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.
git diff-tree --no-commit-id --name-only -r <hash> to list files changed.