pr-reviewlisted

# pr-review ## Overview A code review that evaluates a pull request against four axes — Clean Code, SOLID, DRY, and development best practices — and reports **what is done well** and **what must be fixed**, ending in an explicit verdict. It reviews and reports. It never edits files, commits, or merges. ## When to Use - A PR is open and needs review before merging. - The user asks "review this", "revisá el PR", "is this ready to merge?". - A branch is finished and its quality needs assessing. Skip when: the user wants the fixes *applied* — that is a separate task requiring their explicit go-ahead after this review. Works the same for the user's own PRs and for someone else's — authorship never softens or sharpens a finding. ## Invocation ``` /pr-review <target> [--es|--en] [--comment] ``` | Flag | Effect | |---|---| | `--es` / `-es` | Report in Spanish. **Default when no language flag is given.** | | `--en` / `-en` | Report in English. | | `--comment` | After showing the report, offer to post it on the GitHub PR. | Without `--comment` the report stays in the terminal — nothing is posted. The section headers and verdict values are fixed per language (see **Output format**); the flag switches which set is used, for both the terminal output and the posted comment. ## Getting the diff Ask which target if none was given. Never guess. | Target | Command | |---|---| | GitHub PR number | `gh pr diff <n>` | | GitHub PR URL | `gh pr diff <url>` | | Local branch | `git dif