Skillshare Code Review
Review a skillshare change before it becomes a pull request, or review an open pull...
Install
npx skills add runkids/skillshare --skill skillshare-code-review -g -a claude-code -y- Repository
- runkids/skillshare2.9k
- Category
- Git and review
- Updated
- 3d ago
- License
- MIT
- Context cost
- Lightabout 1,305 tokens
- Runs scripts
- No, instructions only
What it does
Review a skillshare change before it becomes a pull request, or review an open pull request. Use this skill whenever the user asks to: review a diff, branch, commit range or PR, check a change before opening a PR, run a pre-Codex review, or find what a change missed. It checks correctness, the repository's documented rules, the originating issue or spec, every consumer of a changed concept, and cleanup (reuse, simplification, efficiency, depth of fix), then verifies each finding against the code before reporting it. Read-only unless the user asks for fixes.
Review 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.
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.
Before 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.
Step 1: Pin the diff
| $ARGUMENTS | Diff |
|---|---|
| empty | git diff origin/main...HEAD plus git diff HEAD (uncommitted work counts) |
| a ref | git diff <ref>...HEAD plus git diff HEAD |
| 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 |
| a path | that file or directory, reviewed whole |
Run 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.
Step 2: Gather context once
- Spec: in order, issue references in commit messages or the PR body (
gh issue view <n>), a path in $ARGUMENTS, or a matching file inspecs/. If none exists, the Spec pass reports "no spec". - Rules:
AGENTS.md, plus the topics for the touched areas. Runpython3 scripts/ai-context.py listand pick by path:cmd/andinternal/→cli-development;ui/orwebsite/src/→frontend; docs, READMEs,skills/→documentation;wiki/→ai-context. - Concepts: name each flag, field, error, config key, API route, or behavior the diff adds or alters. The Consumer pass sweeps these.
