reviewlisted

# Review: Single-Issue Deep Validation Deep-validate a single GitHub issue against the current codebase. Cross-reference file paths, detect already-implemented features, check for related PRs, verify dependencies, and deliver a structured verdict with recommended action. ## Workflow ```text 1. Auth Check → 2. Detect Repo → 3. Fetch Issue → 4. Parse Body → 5. Codebase Cross-Reference → 6. PR Check → 7. Dependency Check → 8. Verdict → 9. Present Report → 10. Interactive Action ``` ### Step 1: Verify GitHub Auth ```bash gh auth status ``` **On failure:** Stop and tell the user to run `gh auth login`. ### Step 2: Detect Repository ```bash gh repo view --json nameWithOwner -q .nameWithOwner ``` **On failure:** Ask the user for the target repository (`owner/repo`). ### Step 3: Fetch Issue Require an issue number from the user's arguments. If none provided, use `AskUserQuestion` to ask for one. ```bash gh issue view ISSUE_NUMBER --json number,title,body,state,labels,assignees,milestone,createdAt,updatedAt,author,comments ``` **Edge cases:** - Issue doesn't exist → abort with a clear error - Issue already closed → warn but continue (informational analysis is still useful) ### Step 4: Parse Issue Body Classify the issue into one of two tiers based on body structure: #### Tier 1: Structured (created by `/pm`) Detect `/pm` sections by their headers: `## Context`, `## Acceptance Criteria`, `## Implementation Guide`, `## Scope`. Extract: - **File paths** from `## Impleme