resolve-review

Resolve Review Workflow

This workflow guides you through resolving review findings (either local reviews or remote Pull Request comments) inside an isolated Git Worktree using an efficient orchestrator-worker pattern. It keeps the main conversation context clean and focused on user-approved planning, while delegating heavy file-parsing and code-modification tasks to specialized subagents.

Trigger

Use this workflow whenever the user asks to "resolve review", "fix review comments", or "address feedback" from a code review.

[!IMPORTANT] Fresh Fetch Mandate (MANDATORY): When this skill is invoked, the agent MUST ALWAYS fetch/refresh the review comments directly from the live GitHub API as the very first action. Under no circumstances may the agent reuse old, cached, or existing threads or analysis files. A fresh unique query file (e.g. .tmp/pr_threads_<PR_NUMBER>_<TIMESTAMP>.json) must be created, and a fresh query must be executed. Relying on cached comment data is strictly prohibited.

---

🤖 Orchestration & Delegation Mandate

The primary agent MUST act as the orchestrator of the review resolution workflow. To prevent context clutter and manage token usage, the orchestrator:

1. Orchestrates: Handles user approval, high-level task planning, git worktree setup, and final GitHub PR interactions (posting comments and resolving threads).
2. Delegates: Spawns specialized subagents for token-heavy phases (gathering/analyzing findings and implementing specific code fixes), keeping the main chat clear of raw compiler output, lint logs, and long JSON payloads.

---

🌳 Isolated Git Worktree Mandate

To prevent conflicts with ongoing local work and avoid workspace pollution, the agent MUST operate within an isolated Git Worktree:

1. Create Git Worktree: Create an isolated worktree under a designated, git-ignored /worktrees/pr-<PR_NUMBER> directory.
   • If the branch already exists (e.g., the PR's feature branch): checkout the existing branch directly:

     git worktree add worktrees/pr-<PR_NUMBER> <existing_branch_name>
     

   • If creating a new branch: use the -b flag:

     git worktree add -b <new_branch_name> worktrees/pr-<PR_NUMBER> origin/main
     

   • IMPORTANT: Always use the existing PR branch when resolving review comments. Do NOT create a new fix/ branch.
2. Environment Setup:
   • Copy the .env file from the root project directory to the worktree directory: cp .env worktrees/pr-<PR_NUMBER>/.env.
   • Symlink the node_modules directory from the root project directory to the worktree directory to avoid duplicate installation overhead:

     ln -s ../../node_modules worktrees/pr-<PR_NUMBER>/node_modules
     

3. Scoped Operations: All subsequent terminal commands, local testing, code modifications, linting, compiling, and git pushes MUST be executed inside the worktree directory.