Hand a branch the PR description it deserves
Point an agent at a branch you already have — get a real PR write-up.
Who this is for.
You're done with the work. The branch is green. You just don't want to write the PR description, the changelog entry, the migration notes, and the test-plan checklist at 6pm on a Friday. You want an agent that already has the diff, the task definition, and your conventions, and that produces a write-up that matches the actual work — not one that hallucinates a 'refactor' that never happened.
The workflow in 4 steps.
Point the task at the branch you already have
Create a task whose prompt names the branch, the comparison base (`main`), and the artifacts you want: PR description, changelog entry, migration notes, test plan. The agent gets the diff as context, plus your project definition — which is where your team's PR conventions live.
Spell out the conventions in acceptance criteria
Encode the rules: 'must include a `## Test plan` checklist', 'changelog entry follows Keep-a-Changelog', 'migration notes must list every breaking change in the diff'. Generic 'write a PR description' tasks produce generic 'misc fixes' output.
Let the agent read the diff in a clean worktree
The task runs in a worktree checked out at your branch. The agent can `git diff`, `git log`, and read the affected files directly — so the write-up references real symbols, real files, and real commits, not a vague summary of what it 'thinks' the branch did.
Paste, tweak, ship
When the task finishes, the artifacts land in the worktree as plain markdown files (or wherever you asked them to go). Copy into the PR, edit anything that doesn't quite match your voice, and ship. You stop writing 'misc fixes' on a Friday.
A real task you can copy.
Drop this into .watchfire/tasks/<n>.yaml, tweak it to your repo, and start it from the TUI or GUI.
task_id: prep0011
task_number: 11
title: "Draft PR description, changelog, and migration notes for feature/per-org-limits"
prompt: |
The branch `feature/per-org-limits` adds
per-organization rate limiting to every
`/api/*` route. The diff vs `main` is the
full source of truth — do not invent changes
that aren't in it.
Produce three artifacts inside the worktree:
1. `PR_BODY.md` — a PR description with:
- One-paragraph summary.
- "What changed" bullet list, grouped by
area (routes, middleware, tests, infra).
- "How to test" section with concrete curl
commands or test invocations.
- "Out of scope" section listing things this
PR deliberately doesn't do.
2. `CHANGELOG_ENTRY.md` — one entry in
Keep-a-Changelog format under
`### Added` / `### Changed` /
`### Fixed` as appropriate.
3. `MIGRATION_NOTES.md` — only if there's a
breaking change for users of the API. List
each breaking change with the old behaviour,
the new behaviour, and the upgrade step.
No marketing language. No 'this PR cleans up'
unless cleanup is literally in the diff. If
something is uncertain, leave a
`TODO: confirm` line and move on.
acceptance_criteria: |
- `PR_BODY.md` exists and references every
top-level directory touched by
`git diff main...HEAD --name-only`.
- `CHANGELOG_ENTRY.md` is a single,
well-formed Keep-a-Changelog entry.
- `MIGRATION_NOTES.md` exists if and only if
the diff contains an API-breaking change.
- No claim in any artifact contradicts the
actual diff.
status: ready
More starters in the task template library.
Why Watchfire makes this faster.
- The task starts with the full diff and the project definition as context, so the write-up matches the actual work instead of a hallucinated summary.
- Acceptance criteria let you encode your team's PR conventions once — 'must include a test plan', 'changelog must follow Keep-a-Changelog' — and reuse them for every future review-prep task.
- The worktree gives the agent real `git diff` and `git log` access, so it references real file names and real commits, not a paraphrase from training data.
- Run it across half a dozen branches in parallel — every open PR gets its write-up while you're in a meeting.
- The transcript captures what the agent looked at, so if a reviewer questions a claim in the PR body you can trace it back to the diff line it came from.
Related use cases.
Refresh docs from the source of truth
Ship a docs pass page by page — not as one unreviewable docs-mega-PR.
Read the playbook
Switch from raw Claude Code or Codex
Keep the agent you trust — add the seatbelts your working tree doesn't have.
Read the playbook
Refactor a tangled module
Carve a sprawling refactor into scoped diffs you can actually review.
Read the playbook
Get started with Watchfire
Install in seconds. Define tasks. Let agents ship code for you.
Download for macOSAvailable for macOS, Linux, and Windows
# Install via Homebrew (macOS)brew tap watchfire-io/tapbrew install --cask watchfire-io/tap/watchfire# Set up your project and gowatchfire initwatchfire task add "Build the login page"watchfire start --allIncludes GUI, CLI, and daemon. Also available via Homebrew.