← ClaudeAtlas

reviewlisted

Reviews or ships a GitHub pull request or GitLab merge request. Review mode reads the request, runs the conventions, deslop, jsdoc, humanizer, and documentation passes, then asks what to do with each finding and with the request (comment, request changes, approve, fix, or close). Ship mode takes your own branch to merge-ready, including branch name, checks, changeset, commits, title, body, push, and CI. Use when asked to review a PR or MR or whether one is ready to merge, and load it before the first commit whenever work will end in a commit, push, or PR, including a session told to push to a branch.
stijnvanhulle/agents · ★ 2 · Code & Development · score 75
Install: claude install-skill stijnvanhulle/agents
# Review Two modes for a pull request or merge request. Review judges a request someone opened, or one you want checked before merging, and acts only on what the user picks. Ship takes your own branch to merge-ready, in order. Load this skill before the first commit, since the branch name and the commit split are hard to change after a push. ## Review ### 1. Fetch the change Pick the host skill, `github` or `gitlab`, from the input or the remote, and use its commands for every read and write in this mode. The input is `#12`, `!12`, `owner/repo#12`, a request URL, or nothing for the current branch's request. Read the title, body, linked issue, commits, open review threads, CI status, and the diff. When the working tree is clean, check out the branch so the review sees the connected code and can run the checks. Otherwise fetch the branch and read files with `git show origin/<branch>:<path>`. Write the diff to a file outside the working tree for the subagent. Check the claims in the description and commits against the diff. ### 2. Run the passes In Claude Code and Cursor, run the `code-reviewer` subagent with the diff file, tell it whether the branch is checked out, and take its findings for passes 1 to 5. Elsewhere, run the passes yourself, substance before style before prose, reading each skill for its criteria: 1. `conventions` and correctness: logic errors, edge cases, security at trust boundaries, and a test for every code change. 2. `deslop`: the reuse-first la