reviewlisted

# Review Skill Review the requested change and write the result to `review.json`. The review is read-only: do not approve, request changes, comment, merge, push, or otherwise modify remote repositories. ## Select the change source Use the source explicitly named by the user. If it is not named, inspect the current repository and ask when the target is ambiguous. ### Local changes - Run `git status --short` and inspect staged and unstaged changes with `git diff`, `git diff --cached`, and the relevant branch comparison when needed. - Review the working tree as it exists; do not checkout, reset, stash, or amend user changes. ### GitHub pull requests - Read the `gh` skill before using GitHub commands. - Confirm repository context with `git remote -v` or use `--repo OWNER/REPO`. - Read metadata with `gh pr view NUMBER --json title,body,baseRefName,headRefName`. - Read the patch with `gh pr diff NUMBER`. - Use only read operations. Do not run `gh pr review`, `gh pr comment`, `gh api` mutations, or any other publishing command. ### GitLab merge requests - Read the `glab` skill before using GitLab commands. - Confirm repository context with `git remote -v` or use `-R OWNER/REPO`. - Read metadata with `glab mr view NUMBER --output=json`. - Read the patch with `glab mr diff NUMBER`. - Use only read operations. Do not run `glab mr approve`, `glab mr note`, merge, or other mutating commands. ## Review process 1. Establish the change intent from the request, commit hi