# Agentfiles Commit Prefixes

> Repository-local guidance for agentfiles commit subjects using area prefixes instead of Conventional Commits. Use when committing or the user asks to commit.

- Skill: `lhohan/agentfiles-commit-prefixes` (Agent Skill)
- Install (CLI): `npx skillmds@latest add lhohan/agentfiles-commit-prefixes`
- Raw SKILL.md: https://api.skillmd.com/api/skills/lhohan/agentfiles-commit-prefixes/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: lhohan (https://skillmd.com/u/lhohan)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/lhohan/agentfiles-commit-prefixes

---


# 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 under `agents/pi/`
- `dotagents:` — changes under `agents/dotagents/`
- `shared:` — changes under `agents/agents-shared/`
- `vibe:` — changes under `agents/vibe/`
- `zerostack:` — changes under `agents/zerostack/`
- `docs:` — documentation changes (only)
- `build:` — task management or build related changes
- `chore:` — 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 footer`
- `build: update stow task documentation`
- `shared: review and update canonical AGENTS.md content`
- `docs: 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