skillshare-code-review

1Review one change in five independent passes, verify every finding, and report them by pass. $ARGUMENTS names the target (a base ref, a PR number, or a path) and may end with `fix`.
2 
3**Scope**: Read-only by default. With `fix`, apply findings as the end of Step 5 describes. Never commit, push, or comment on GitHub unless the user asks.
4 
5Before acting, run `python3 scripts/ai-context.py pull-requests`. Its Review Rounds section defines what a review must sweep before Codex sees the change; this skill is how that sweep runs.
6 
7## Step 1: Pin the diff
8 
9| $ARGUMENTS | Diff |
10|---|---|
11| empty | `git diff origin/main...HEAD` plus `git diff HEAD` (uncommitted work counts) |
12| a ref | `git diff <ref>...HEAD` plus `git diff HEAD` |
13| a PR number | check the PR out in a new scratch worktree (`git worktree add`, then `gh pr checkout <n>` inside it) and review there with `git diff origin/<base>...HEAD`, so Step 4 reads the PR's code, not the current branch |
14| a path | that file or directory, reviewed whole |
15 
16Run `git fetch origin` first so the base is current. Stop here if the ref does not resolve or the diff is empty. In a shared checkout, list files changed by another session (`git status`) and leave them out of scope.
17 
18## Step 2: Gather context once
19 
201. **Spec**: in order, issue references in commit messages or the PR body (`gh issue view <n>`), a path in $ARGUMENTS, or a matching file in `specs/`. If none exists, the Spec pass reports "no spec".
21…