/nova-rework

After /nova-wrap you have a PR open. The reviewer reads your code and leaves comments asking for changes. /nova-rework handles that round of changes coherently — fetches feedback, generates tasks, executes them. Then you run /nova-review to verify and /nova-wrap to commit and push.

/nova-rework

What it solves

/nova-build is for the initial implementation based on tasks.md. After /nova-wrap runs, tasks.md has every task marked [x], so /nova-build says "all done, run /nova-review" — which isn't what you need after a reviewer asks for changes.

You could edit tasks.md by hand and run /nova-build again, but that's fragile and easy to mishandle. /nova-rework:

• Fetches PR comments via gh or glab (or accepts paste)
• Translates each actionable comment into a task in a new ## Review fixes (round N) section
• Executes the new tasks with the same self-check discipline as /nova-build
• Re-runs deterministic checks (review-checks.sh)

What it doesn't do

• Doesn't commit or push. Run /nova-review then /nova-wrap — wrap detects the existing PR and only commits + pushes.
• Doesn't create a new PR. /nova-wrap pushes to the existing branch, which updates the PR automatically.
• Doesn't touch Jira. Ticket state is managed manually after /nova-start sets it to "In Progress".

Typical session

> /nova-rework

[fetches gh pr view --comments]
[generates 3 tasks under "## Review fixes (round 1)"]

Show user:
  ## Review fixes (round 1)
  - [ ] @alice: use Result<T,E> instead of throwing in validateUser → src/auth/validate.ts
  - [ ] @alice: add test for empty-email edge case → src/auth/validate.test.ts
  - [ ] @bob: rename `auth` constant to `authMiddleware` → src/auth/index.ts

Proceed? (y/n)

[executes tasks, marks [x] one by one]
[runs review-checks.sh — passes]

## Round 1 ready
- Comments addressed: 3
- Files touched: src/auth/validate.ts, src/auth/validate.test.ts, src/auth/index.ts
- Deterministic checks: ✓

Next: run /nova-review to verify, then /nova-wrap to commit and push.

> /nova-review  →  ✓

> /nova-wrap    →  detects PR exists → commits + pushes
  Commit: abc1234 review(auth): address round 1 feedback from @alice, @bob
  Pushed to: feature/PROJ-42-validate-auth
  PR: https://github.com/your/repo/pull/123 (waiting for re-review)

Multiple rounds

Each invocation creates a new section:

## Review fixes (round 1)
- [x] @alice: use Result<T,E> instead of throwing
- [x] @alice: add test for empty email
- [x] @bob: rename auth constant

## Review fixes (round 2)
- [x] @alice: nit — extract magic number 30s to a named constant
- [x] @bob: ah I see, ignore my round-1 comment about the name — undo it

tasks.md is the audit trail of the whole review cycle. Anyone reading it later can reconstruct the back-and-forth without digging through PR comments.

When something in feedback isn't a code change

Feedback type	What to do
"LGTM" / approval	Nothing. /nova-rework doesn't create tasks for approvals.
Question you can answer in a reply	Reply on the PR. No task needed.
Nit you choose to skip	Tell /nova-rework to drop that task when it shows you the list.
Suggestion that contradicts the spec	Stop. Update proposal.md (or re-run /nova-spec) first.
Suggestion that requires a new architectural decision	Stop. Write the decision in context/decisions/<concept>.md first. Then resume.

When the reviewer is satisfied

You don't do anything special. When they approve and merge the PR, the merge commit lands on main (or your branch.base) and you're done with the ticket.

Jira state after that is yours to manage — move it to Done manually or via your team's forge integration.

Errors you may see

Error	Cause	Fix
No PR found on current branch	/nova-wrap wasn't run, or branch isn't pushed	Run /nova-wrap first
gh: command not found	GitHub CLI missing	Install gh or paste the review comments manually
Deterministic checks failed (lint/tests)	The fix broke something	Read the script output, address, retry
tasks.md not found	Quick-fix ticket without tasks.md	/nova-rework creates one with just the review-fixes section

Companion commands

• /nova-wrap — produces the PR that this command reworks
• /nova-build — initial implementation. Don't reuse for review fixes.
• /nova-review — local pre-PR review, before /nova-wrap. Distinct from human PR review.