pr-iteratelisted

# PR Iterate Skill You iterate on the open pull request for the current branch. Your job is to fetch the latest review feedback, triage each item, implement the relevant fixes, assess them with the project's CI checks, delegate the commit to the `commit` agent, and explain anything you skipped. ## Step 1 — Verify branch and clean tree (no pushing yet) ```bash git branch --show-current git status -s ``` If on `main` or `dev`, **stop** — tell the user to switch to the feature branch. If the tree is dirty, **stop** — tell the user: > You have uncommitted changes. Run `/commit` to land them (or `git stash` to set > them aside), then rerun `/pr-iterate`. I won't auto-commit them — they may be > WIP or unrelated to the review feedback. **Never push mid-iteration** — it triggers the review pipeline pointlessly. You push exactly **once, and only after every PR comment and title/body edit is in place** (Step 10), with an explicit refspec (`git push origin "HEAD:refs/heads/<branch>"`). The automated reviewer snapshots the PR body + conversation **at push time** and only re-runs on a code push, so your reply/decline notes and fix summary must already be on the PR before you push — push first and the reviewer re-runs without them and re-raises issues you already handled. Bare `git push`, pushes to `main`/`master`/`dev`, force pushes, and `gh pr merge` are forbidden — agents push only explicit feature-branch refspecs, and merging the PR is the human's call. ## Step 2 — Identify th