reviewkit
Installation
SKILL.md
reviewkit
Review agent-written code in four passes; report findings, and never edit source, commit, or push. A correctness-only request runs only the Correctness pass.
Review with fresh eyes
Delegate the passes to a fresh subagent with the diff, the stated intent, and the passes below; review its findings, then present them. When no subagent tool is available, run the passes yourself and label the report a self-review. Either way, judge the code on disk, not the code you remember intending to write.
Procedure
1. Pick the review target
Ground the review in an actual diff. Detect the target from git state, then state your pick and let the user override:
- Uncommitted changes present (
git status --porcelainis non-empty) → review the working tree:git diff HEAD(include staged withgit diff --staged). This is the default after a fresh coding session.git diffdoes not show untracked files, so a brand-new file an agent never staged is invisible to it. List them withgit status --porcelain(the??entries) orgit ls-files --others --exclude-standard, andReadeach one in full as part of the change: every untracked source file, no exceptions. The only untracked files you may skip are ones nobody wrote: lockfiles, build output, vendored dependencies, compiled assets, snapshots. Note them as generated, spot-check that they're actually generated rather than hand-edited, and move on. - Clean tree, branch ahead of its base → review the branch diff. Get the base branch from gitkit, which owns that resolution; a wrong base yields an empty diff or half the repo's history, and both look like a real review target. Without gitkit, take the remote default branch from
git symbolic-ref --short refs/remotes/origin/HEAD(strip theorigin/prefix), else the first ofmainormasterthatgit rev-parse --verifyresolves, and say in the target line which fallback you used. Then rungit diff <base>...HEADandgit log <base>..HEAD --onelinefor intent. - If the invocation names a target ("review the branch", "review my staged changes") → honor it directly, skip detection.
Say which target you chose and why in one line, then proceed. If neither applies (clean tree, no branch ahead), ask what to review rather than guessing.