The commit prompt
The whole text of config/agent-prompts/commit.md, as an agent is handed it.
Bundled agent prompts — one row of 23, exported from
config/agent-prompts
· every prompt
· the resolution order
What this prompt is
| id | commit | the key every tier, every pattern step and every override spells it by |
| kind | not a stage instruction | whether any bundled pattern hands it to an agent step |
| role | — | the harness role the agent reading it runs under |
| stage | — | the stage of a run it is handed at |
| bundled at | config/agent-prompts/commit.md | where the built-in copy sits in Gantry's own tree |
No bundled pattern hands this file to an agent step.
Where an override of it goes
| tier | the file to write | what it is |
|---|---|---|
|
run
consulted 1st |
.gantry/<plan>/prompts/commit.md |
the run's own frozen copy, written when the run started and read by every agent it launches; editing it changes what a run's remaining agents are told |
|
project
consulted 2nd |
.gantry/<plan>/commit.md |
a per-run override an operator places beside the run's other orchestration files |
|
global
consulted 3rd |
~/.config/gantry/agent-prompts/commit.md |
the materialized global mirror; it overrides the built-in once its bytes differ from the built-in's |
|
built-in
consulted 4th |
config/agent-prompts/commit.md |
the default compiled into the binary |
The text
You are writing the git commit message for a change gantry's pipeline just produced. The staged diff is
below. Output **only** the commit message — no preamble, no code fences, no trailing commentary.
Write:
- A concise subject line in the imperative mood, ≤ 72 characters. Use a conventional-commits prefix
(`feat:`, `fix:`, `refactor:`, `test:`, `docs:`, `chore:`) when one clearly fits.
- A blank line, then a short body (a few lines, wrapped ~80 cols) explaining **what** changed and
**why**, at the level a reviewer skimming history would want. Mention the load-bearing files or
functions when that aids understanding.
Describe only what the diff actually shows — never invent rationale you cannot see. Name files,
functions, and flags exactly as the diff spells them — no metaphor or generality where the
identifier is available. If the diff is trivial, a single subject line with no body is fine.
Staged diff:
{{DIFF}}