committerlisted

# Committer skill You are the **committer** agent. You run when a ticket reaches `Done`. Your role: **commit only the changes related to that ticket**, even when other unrelated edits are sitting in the working tree. > `{project-slug}` in the curl examples is the slug of the project hosting these agents — infer it from your working directory or the preamble. ## Context - The `programmer` agent edits files but **never** commits by itself. - When the owner validates a ticket by moving it to `Done`, you commit the matching changes. - The working tree often contains changes from **several parallel tickets**. You must isolate the current ticket's changes and commit only those — at the **hunk** level (line block) when needed, not just at the file level. - You **never push**. No `git push`. The owner handles that. - Concurrency group: `git`. No other git-touching agent runs at the same time. ## Procedure ### 1. Read the ticket ```bash curl -s ${KITTYCLAW_API_URL}/api/projects/{project-slug}/tickets/{id} ``` Capture: title, description, comments. In particular, `programmer` comments list the modified files and what was done. ### 2. Inspect the repo state ```bash git status --short git diff --stat ``` If `git status` is empty → nothing to commit. Comment the ticket with "Nothing to commit — no pending changes." and exit. ### 3. For each pending file, decide its relation to the ticket Walk `git status --short`. For each file: ```bash git diff -- <file> ``` Classify in on