# Skillshare Code Review

Review a skillshare change before it becomes a pull request, or review an open pull...

- Repository: https://github.com/runkids/skillshare (2879 stars)
- Category: Git and review
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add runkids/skillshare --skill skillshare-code-review -g -a claude-code -y`
Codex: `npx skills add runkids/skillshare --skill skillshare-code-review -g -a codex -y`
Cursor: `npx skills add runkids/skillshare --skill skillshare-code-review -g -a cursor -y`
Gemini CLI: `npx skills add runkids/skillshare --skill skillshare-code-review -g -a gemini-cli -y`

## Description

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.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

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

1. **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".
2. **Rules**: `AGENTS.md`, plus the topics for the touched areas. Run `python3 scripts/ai-context.py list` and pick by path: `cmd/` and `internal/` → `cli-development`; `ui/` or `website/src/` → `frontend`; docs, READMEs, `skills/` → `documentation`; `wiki/` → `ai-context`.
3. **Concepts**: name each flag, field, error, config key, API route, or behavior the diff adds or alters. The Consumer pass sweeps these.

## Step 3: Run five passes in parallel

The rest: https://github.com/runkids/skillshare/blob/HEAD/.skillshare/skills/skillshare-code-review/SKILL.md