Repository navigation
docs: commit scopes for new integration packages #36
Description
Area
Docs
Problem
CONTRIBUTING.md lists cursor and antigravity as commit scopes for the existing integration packages, but there isn't a scope yet that fits a new integration. While preparing #34 (a Claude Code hooks package in packages/tiny-engineer-claude-code) I wasn't sure which scope to use, so I went with feat(packages): … for now, although packages isn't on the list either.
Proposed change
Whichever you prefer:
- Add a scope for each integration as it lands (e.g.
claude-code) - Add one general scope, such as
packagesorintegrations, for anything underpackages/ - Keep the list as it is and have new integrations omit the scope
Happy to update #34's title to match whichever you choose. Thanks!
Activity
jamro commentedon Sep 14, 2026
Chose
integrations— one scope for everything underpackages/(Cursor, Antigravity, Claude Code, later agent CLIs). Per-package scopes (cursor,antigravity,claude-code) would grow with every new agent.CONTRIBUTING.mdand the commit rule now listintegrationsinstead ofcursor/antigravity. Please retitle #34 tofeat(integrations): add Claude Code hooks CLI(done on the PR).Old
feat(cursor)/feat(antigravity)commits stay as-is.docs: Add integrations commit scope #36
Merge upstream/main into upstream/carrier-board-pcb