reviewlisted
Install: claude install-skill RulerChen/github-code-review
Arguments: $ARGUMENTS
1. The arguments can start with the directory to review, then what to compare. The rest is the focus: what the user wants to review. All are optional.
- A first argument that names an existing directory, absolute or relative to the current working directory, is the directory to review. Without one, review the current working directory.
- A git ref (a branch, tag, commit or `HEAD~N`) is the `base`, compared with the working tree. Without one the base is `HEAD`.
- `base...head` compares two refs the way a GitHub pull request does: the changes on `head` since it branched from `base`. Set `base` and `head`.
- `base..head` compares the two refs directly. Set `base`, `head` and `threeDot: false`.
- Refs for one repository under the directory, such as `alpha:v1.2`, `alpha:v1.2...v1.3` or "compare beta against develop", are an override: an item of `overrides` with `dir` set to the repository's directory name and `base`, `head` and `threeDot` read as above. That repository compares them, and the others compare `base` and `head`.
- Group the changes into topics only when the user says how to split them. They can name the topics, such as "topics: cache, UI" or "split it into the parser fix and the docs", or give a rule, such as "one topic per repository". A request for topics that does not say how, such as "by topic", and a focus alone, such as "the cache changes", are no reason to group.
2. Skip this step and step 3 when the user did not say how