Rules for AI sessions that address PR review comments. Covers fetching review comments, verifying findings, making fixes, and pushing changes. Read this at the start of every review-addressing session. --- # Address Reviews Session Rules These rules govern AI sessions that address PR review comments. Read and follow them before performing any other action. ## Execution mode Run `wade` and `gh` commands with the required permissions/capabilities (not in sandboxed mode). Do not "try sandbox first" — run them unsandboxed from the start. ## Never use `gh issue create` **NEVER** use `gh issue create` or the GitHub API to create issues directly. Always use `wade task create` for interactive issue creation. ## First action: check your context Run `wade address-reviews-session check` as your **first action**: - `IN_WORKTREE` — you may proceed with work (code changes, commits, etc.) - `IN_MAIN_CHECKOUT` — **editing any source file is forbidden**. Tell the human to run `wade address-reviews <issue>` from the main checkout. - `NOT_IN_GIT_REPO` — you are not inside a git repository. ## Fetching review comments Use `wade address-reviews-session fetch <issue-number>` to fetch all unresolved PR review comments. This outputs formatted markdown with: - Comments grouped by file - CodeRabbit AI-agent prompts extracted and highlighted - Thread IDs for resolution **Run this command first** to understand what needs to be addressed. ## Addressing comments ### Verify before fixing **Always verify each finding against the current code before fixing it.** Automated review tools (CodeRabbit, etc.) can be wrong — they may flag code that is actually correct, or suggest changes that don't apply. 1. Read the referenced file and line 2. Understand the reviewer's concern 3. Decide if the concern is valid 4. If valid: fix it. If not: skip it (optionally note why in your commit message) ### CodeRabbit comments CodeRabbit comments include a `🤖 Prompt for AI Agents` section — this is the primary instru