Agentfiles Commit Prefixes
Use this skill when writing commit messages for this repository.
Goal
Use a short area prefix that tells the reader what part of the repository changed. This is not traditional Conventional Commits.
Current prefix map
pi:— changes underagents/pi/dotagents:— changes underagents/dotagents/shared:— changes underagents/agents-shared/vibe:— changes underagents/vibe/zerostack:— changes underagents/zerostack/docs:— documentation changes (only)build:— task management or build related changeschore:— repository-wide or cross-cutting changes, including root files, task scripts
If a change touches one package plus repo-wide docs, choose the prefix that best matches the primary intent.
If no single prefix clearly dominates, use chore:.
Message shape
Format:
<prefix>: <imperative summary>
Examples:
pi: show all bookmarks in jj footerbuild: update stow task documentationshared: review and update canonical AGENTS.md contentdocs: document the commit prefix convention
Keep the subject short, direct, and in present tense. Add a body only when the rationale needs explanation.
Maintenance rule
Update this skill whenever the repository evolves:
- add a new prefix for each new direct
agents/<name>/package - revise the
chore:definition when repo-wide files or workflow change - keep examples in sync with real commit history