Commit Categories
- 35 installs
- 8.5k repo stars
- Updated August 5, 2026
- cloudflare/workerd
commit-categories groups workerd commits by changed paths for release notes.
About
The commit-categories skill provides canonical path-based grouping for workerd commits into API, Node.js compat, Python, Rust, Cloudflare APIs, I/O, JSG, Server, Build, Types, Docs, Tests, or Other. Cross-cutting callouts highlight New or Updated Compat Flags and Autogates separately from primary categories. Categorization uses git diff-tree file lists and majority path matching. Must load before changelog or whats-new commit categorization commands. Use when building release notes or summarizing workerd commit batches.
- Path-pattern table for primary commit categories.
- Separate callouts for compat flags and autogates changes.
- Majority-path rule for multi-area commits.
- Uses git diff-tree per commit file lists.
- Required before changelog categorization commands.
Commit Categories by the numbers
- 35 all-time installs (skills.sh)
- Ranked #149 of 248 Release Management skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
commit-categories capabilities & compatibility
- Capabilities
- commit category path table
- Use cases
- documentation
What commit-categories says it does
Categorize commits by the files they touch
npx skills add https://github.com/cloudflare/workerd --skill commit-categoriesAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 35 |
|---|---|
| repo stars | ★ 8.5k |
| Last updated | August 5, 2026 |
| Repository | cloudflare/workerd ↗ |
How do I categorize workerd commits for a changelog?
Categorize workerd commits by path for changelogs and release notes.
Who is it for?
Release note authors summarizing workerd commit history.
Skip if: Skip for single-commit reviews without changelog needs.
When should I use this skill?
Categorizing commits for changelog or whats-new output.
What you get
Commits grouped by API, I/O, Build, and compat flag callouts.
Files
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.
Related skills
Changelog AutomationAutomatically generate accurate, well-structured changelogs from commit history and Conventional Commits.11.2k38.5k
Msstore CliAutomate publishing, managing submissions, and handling CI/CD for Windows apps in the Microsoft Store.7k37.5k
Changelog GeneratorAutomatically turn git commit history into polished, customer-friendly release notes without manual rewriting.5.9k71.8k
Deploy ChecklistGenerate a complete pre-deployment verification checklist tailored to their service or release.4.6k23.3k
Opensource PipelineSafely strip secrets, sanitize code, and generate required open-source files before releasing a private project publicly.4.3k238k
Community PublishInstantly share running services with public URLs, list projects on a discoverable dashboard, or open-source code to a community GitHub repository.3.9k21FAQ
What does commit-categories do?
commit-categories groups workerd commits by changed paths for release notes.
When should I use commit-categories?
Categorizing commits for changelog or whats-new output.
Is this skill safe to install?
Review the Security Audits panel on this page before installing in production.