forge-prlisted

# forge-pr Automate the close step: turn a verified unit into a clean branch, commit, and PR. Only run this once the unit is implemented AND verified. ## Preconditions - The unit's verification passed (run `forge-verify` first if unsure). For a last-mile sanity check on risky changes, the `forge-reviewer` agent can review the final diff before pushing. - `progress-tracker.md` shows the unit as complete or ready to close. - The repo is a git repository with a clean-enough working tree for this unit's changes. ## Argument Text after the command selects the unit and optionally the base branch (e.g. `/forge-pr unit 04` or `/forge-pr 04 onto develop`). No argument → take the unit marked complete/ready-to-close in the tracker. Either way, confirm the unit and the base branch (default `main`) with the user before pushing. ## Steps ### 1. Branch Create/switch to a branch named `feat/NN-feature-name` matching the unit (use `fix/` for bug-fix units, `chore/` for tooling). Check current branch and status first. ### 2. Stage and commit Stage the unit's changes. Write a Conventional Commit message: ``` feat(scope): short summary of the unit - key change 1 - key change 2 Implements unit NN per context/specs/NN-feature-name.md ``` Use `feat:`, `fix:`, `chore:`, `refactor:`, `docs:` as appropriate. Keep the subject under ~72 chars. Do not bundle unrelated changes — one unit per PR. ### 3. Push and open the PR Push the branch. Open a PR (via `gh pr create` if the GitHub CL