Why Writing Code Isn’t the End: How Superpowers Handles Review, Git Worktrees, and Branch Finalization

Even after the code is written, the Superpowers system does not consider the job finished. It enforces three critical skills— requesting-code-review, using-git-worktrees, and finishing-a-development-branch —to prevent common pitfalls such as unchecked changes, polluted workspaces, and ambiguous hand‑offs.

Why Code Review Matters

Superpowers treats code review as an engineering gate, not a casual glance. Review must happen after each task, after a large feature, and before any merge. Reviewers must provide the BASE_SHA, HEAD_SHA, the actual changes, and the related plan or requirement, ensuring the review checks whether the change still satisfies the original intent.

Two failure modes are highlighted:

Blindly applying external feedback without verification.

Accepting feedback superficially without confirming the problem scope.

Superpowers mandates a disciplined response: understand the feedback, verify its relevance, then decide whether to apply it.

Isolating the Implementation Environment with Git Worktrees

The using-git-worktrees skill is not a fancy Git trick; it solves the problem of implementation‑stage contamination. Risks include mixing current work with unrelated changes, dirty test baselines, and difficulty switching back to the main branch.

Superpowers’ process isolates work before implementation:

Choose a worktree location.

Ensure the directory is ignored in .gitignore if it resides inside the project.

Create a new worktree and branch.

Run project initialization.

Execute baseline tests to confirm a clean environment.

This mirrors a pre‑deployment check, guaranteeing that any later decision is based on a known‑good state.

Closing the Development Loop

The finishing-a-development-branch skill formalizes the end of a development cycle. It does more than merge or open a PR; it follows a strict sequence:

Re‑run tests to verify the current baseline.

Confirm the base branch.

Present four fixed options: local merge, push & PR, keep the branch/worktree, or discard the work.

Execute the chosen action and clean up the worktree if needed.

This prevents common “last‑minute” mistakes such as merging without retesting, pushing with unresolved branch relationships, or discarding work without explicit confirmation.

Unified Goal of the Skill Set

When viewed together, the three skills address a single problem: turning "code written" into "a complete, traceable, and safely concluded engineering task." They guard against unchecked changes, polluted environments, and vague hand‑offs, ensuring that every delivery is backed by evidence, clear boundaries, and controlled cleanup.

Superpowers therefore differs from many AI‑assisted coding flows, which focus on speed and automation. Instead, it emphasizes rigorous process, making the final mile of development as reliable as the earlier stages.