review-with-intentlisted

# Goal Validate that code changes actually do what they are supposed to do. Extracts the intended behavior from a user-provided source (GitHub issue, pasted spec, free-form description), then review the diff against that intent — surfacing where the code matches, where it diverges, what is missing, and whether the implementation quality is sound. # Inputs Expected input from the user: - **Intent source** — one of: - a GitHub issue number (e.g. `#42`) - a GitHub issue URL - pasted text (spec, ticket body, acceptance criteria, user story) - free-form description of the goal - **Changes to review** — one of: - current branch diff vs main (default) - a specific PR number or URL - a named branch - an explicit commit range If intent source is missing but a PR is provided, check the PR description for linked issues (e.g. `Closes #42`, `Fixes #42`, bare `#42` references) before asking — fetch the linked issue and use it as the intent source. Only ask if no intent can be found this way. # Tools and environment assumptions - Current working directory is a local clone of the target repository - `gh` is installed and authenticated (for fetching GitHub issues or PR diffs) - `git` is available # High-level behavior Follow this approach strictly in order: ## Step 1 — Extract intent Extract the structured intent from the provided source. Produce: - **Goal** — one-sentence summary of the intent - **Scope** — what is in and out of scope (inferred if not explicit) -