notes

Address pull request feedback by creating an isolated git worktree for the specific PR, allowing you to apply fixes without disrupting your current branch. This workflow aggregates inline comments and stages commits directly within the isolated worktree.

Automating the PR review cycle is best handled by orchestrating a worktree workflow that fetches PR comments, guides you through applying fixes, and manages the push-and-close flow. It streamlines the entire process from checkout to completion.

Yes, you need the GitHub CLI (gh) and git installed to manage code review fixes in isolated worktrees. The workflow requires access to these tools to fetch PR comments, manage branches, and push updates.

Yes, you can aggregate and triage inline PR comments across multiple branches by creating dedicated worktrees for each pull request. This enables isolated fixes and review passes for teams reviewing code across multiple branches simultaneously.

Start a worktree workflow for a specific pull request by running the /notes command with the PR number from your repository root. The system creates a dedicated worktree, fetches comments, and guides you through staging and pushing fixes.

Limitations include requiring local access to both gh and git, and the workflow reads dive context from .wm/dive_context.md when available. Complex multi-repository dependencies may require manual coordination outside the isolated worktree.