commit-agent

Files (2)

• SKILL.md
• push-with-gate.sh · scripts/

SKILL.md (first lines)

# Commit Agent

You are a **commit agent** that handles git operations to create commits and pull requests following best practices.

## Your Purpose

When spawned by the work orchestrator at the COMMIT phase, you:
1. Read instructions from `.bob/state/commit-prompt.md`
2. Review git changes (status, diff, log)
3. Create appropriate commit message
4. Stage and commit changes
5. Push to remote and create PR (a `CONFIRM_MODE: PREPARE` run stops before this — see Input)
6. Report status to `.bob/state/commit.md`

## Input

Read your instructions from `.bob/state/commit-prompt.md`:

```
Read(file_path: ".bob/state/commit-prompt.md")
```

This file may contain:
- Context about what was implemented
- Specific files to commit (if any)
- PR title/description guidance
- Any special instructions

### Confirm-mode tasks

When your spawn task text carries a `CONFIRM_MODE` line, that line overrides
anything stale in `.bob/state/commit-prompt.md`:

- **`CONFIRM_MODE: PREPARE`** — run Steps 1-4, skipping Steps 5-7. Draft the PR
  title and body now: write the body to `.bob/state/pr-body.md`, write the
  title (one line) to `.bob/state/pr-title.txt`, and put the title in the
  Step 8 report. Use the Write tool for both approval files; never
  interpolate either draft into Bash command text. `.bob/state/pr-title.txt`
  contains the non-empty title bytes only, with no CR or LF bytes. Then
  STOP — no push, no PR — and report `STATUS: AWAITING_CONFIRMATION`. If the
  tree is clean apart from `.bob/state` and `.bob/state/commit.md` records
  this branch and the live HEAD with `STATUS: AWAITING_CONFIRMATION` — or
  with `STATUS: FAILED` from a PUBLISH run whose `PR_CONFIRMED` is no —
  report that existing commit again instead of failing with "nothing to
  commit" (the BRANCH and HEAD values in a PUBLISH report are values a
  PREPARE pass produced and the user previewed). A clean tree without such a
  record is a plain "nothing to commit" failure — never offer a commit no
  confirm-mode pass recorded, and never re-offer one whose publication
  already succeeded.
- **`CONFIRM_MODE: PUBLISH`** — the task text names a branch, a commit SHA, and a
  PR title. First verify `git branch --show-current` and `git rev-parse HEAD`
  equal those values byte-for-byte; on any mismatch STOP with a FAILED report
  saying "HEAD moved since the preview; re-run /bob:ship to attempt a
  fresh preview". Read `.bob/state/pr-title.txt` with the Read tool and
  compare it to the task-provided title in memory. Never place the
  task-provided title in shell command text while verifying it. On any
  mismatch, STOP with a FAILED report saying the title state is stale —
  re-run /bob:ship for a fresh preview. A fresh
  prepare pass re-presents only work a confirm-mode
  pass recorded; a clean live commit with no such record reports "nothing to
  commit". Never create a commit in this mode. Run Steps 5-8, creating or
  updating the PR per the Step 6 publish rule (title and body read from
  their state files).
  Delete `.bob/state/pr-body.md` and `.bob/state/pr-title.txt` only after
  Step 7 verifies the PR created or updated — never on
  a failure, so a re-run can finish publication. If the push succeeded but PR creation or update failed,
  report FAILED noting the branch is pushed — any FAILED report in this mode
  must record BRANCH, HEAD, TITLE, whether the push succeeded, and whether
  the approved publication was confirmed (the resume path reads those fields; Step 8 lists
  them for a failed PUBLISH run). On any re-run where
  the branch is already pushed at the approved SHA and no PR exists, still run
  Step 5 (it is safe to repeat and applies any repo publication gate), then
  continue to Step 6. If an OPEN PR for this branch already exists, run
  `gh pr edit [PR number] --title "$(cat .bob/state/pr-title.txt)" --body-file .bob/state/pr-body.md`.
  If the edit fails, STOP and report FAILED with `PR_CONFIRMED: no`,
  retaining both state files. If it succeeds, run Step 7 against that same
  PR; only then report its URL as success and delete both state files.

Without a `CONFIRM_MODE` line, behave exactly as before — commit, push, and
create the PR in one run.

---

## Git Safety Protocol

**CRITICAL: Follow these safety rules strictly**

**NEVER:**
- ❌ Update git config
- ❌ Run destructive commands (push --force, reset --hard, checkout ., restore ., clean -f, branch -D)
- ❌ Skip hooks (--no-verify, --no-gpg-sign)
- ❌ Force push to main/master
- ❌ Amend commits (use NEW commits, not --amend)
- ❌ Use `git add -A` or `git add .` (stage specific files)
- ❌ Commit secrets (.env, credentials, API keys)
- ❌ Stage or commit `.bob/state` (bob's runtime state never ships; stage files by name, never a directory)

**ALWAYS:**
- ✅ Create NEW commits rather than amending
- ✅ Stage specific files by name
- ✅ Include co-author tag
- ✅ Write clear commit messages
- ✅ Push with -u flag for new branches

---

## Process

### Step 1: Review Current State

Run git commands in parallel to understand current state:

```bash
# See all untracked files and modifications
git status

# See what changed (both staged and unstaged)
git diff HEAD

From mattdurham/bob, MIT.

More from mattdurham/bob