Menu
Review changes in the current Git branch and suggest improvements. Triggers: "review branch", "review changes", "code review".
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Implement a feature documented in the SPF feature registry. Consumes a feature doc at internal/design/spf/features/<name>.md and produces the engine-side code: new behaviors, updates to existing behaviors, media-layer / network-layer primitives, and tests. The implementation analog of /spf-document-feature (which produces the doc; this consumes it). Walks through resolving the doc's open questions before coding, maps phases to discrete chunks, applies the SPF conventions catalog, routes to downstream skills (/spf-create-behavior, /spf-update-behavior, /refactor-behavior) per chunk shape, and updates the feature doc's Status / Implementation surface / Verification sections as code lands. Triggers: "implement feature", "implement SPF feature", "build feature", "code feature", "scope feature implementation", "implement <feature-name>".
Create a new SPF behavior with conventions-aligned shape. Walks through purpose articulation (carries /refactor-behavior's purpose-first discipline), signal type choice, slot map design, composition placement, cleanup pattern selection, test placement, and engine wiring. Distinct from /refactor-behavior (which modifies an existing behavior preserving its purpose) and /spf-update-behavior (which modifies an existing behavior whose purpose is changing). Triggers: "create behavior", "new behavior", "create SPF behavior", "add behavior", "scaffold behavior", "new SPF behavior".
Produce or update an entry in the SPF use-case-composition registry at internal/design/spf/use-cases/. Triangulates context from multiple sources (Notion, GitHub, pasted writeups, existing use-case docs, constituent feature docs, codebase), grounds the use case in the four composition mechanisms (subtract / add / alternative-impl / alternative-default-config), applies use-case-specific cross-cutting concern checks, drafts the doc at the appropriate definition depth, and cascades narrow updates to constituent feature docs and sibling use cases. Triggers: "document use case", "register use case", "use case doc", "update use case doc", "deepen use-case stub", "new SPF use case", "use case composition", "draft use-case registry entry", "new use case composition".
Implement a use-case composition documented in the SPF use-case-composition registry. Consumes a use-case doc at internal/design/spf/use-cases/<name>.md and produces the engine-side code: a variant engine factory, a parallel adapter, composition wiring, use-case-specific behaviors (if any), and tests. The implementation analog of /spf-document-use-case (which produces the doc; this consumes it). Walks through disambiguation + routing (verify the request is actually a use case, check constituent-feature implementation status), resolves the doc's open questions with the user, maps phases to chunks, routes to downstream skills (/spf-implement-feature for unimplemented constituents, /spf-create-behavior, /spf-update-behavior, /refactor-behavior), and updates both the use-case doc and constituent feature docs as code lands. Treats the use-case doc as a starting point for planning, not a hardened specification. Triggers: "implement use case", "implement SPF use case", "implement use-case composition", "build use ca
Update an existing SPF behavior whose purpose is changing or expanding. Distinct from /refactor-behavior, which preserves purpose — this skill handles cases where the behavior gains new responsibility (new state slot to react to, new lifecycle phase, new constraint, new code path). Carries /refactor-behavior's purpose-first discipline applied to the *purpose change*. Triggers: "update behavior", "extend behavior", "modify behavior", "change behavior purpose", "expand behavior responsibility".
Produce or update an entry in the SPF feature registry at internal/design/spf/features/. Triangulates context from multiple sources (Notion, GitHub, pasted writeups, existing feature docs, codebase), grounds the feature in the cluster heuristics, applies cross-cutting concern checks, drafts the doc at the appropriate definition depth, and cascades narrow updates to related feature docs. Triggers: "document feature", "register feature", "feature doc", "update feature doc", "deepen feature stub", "draft feature registry entry", "new SPF feature".
| name | review-branch |
| description | Review changes in the current Git branch and suggest improvements. Triggers: "review branch", "review changes", "code review". |
| allowed-tools | Bash(git:*), Bash(gh:*), Glob, Grep, Read, mcp__github__* |
| agent | plan |
| context | fork |
Inspect the changes made in this Git branch. Identify any possible issues and suggest improvements. Do not write code. Explain the problems clearly and propose a brief plan for addressing them.
/review-branch [issue]
issue (optional): GitHub issue number or URL for additional context/review-branch
/review-branch 123
/review-branch https://github.com/videojs/v10/issues/123
$ARGUMENTS
If an issue number or URL was provided above, fetch the issue details using GitHub tools to get additional context.
You are an experienced software developer with expertise in code review.
git diff --name-only $(git merge-base HEAD main)...HEAD to list changed filesgit diff $(git merge-base HEAD main)...HEAD to see the full diffCategorize the changed files to determine which review criteria apply:
| File Pattern | Category | Skills |
|---|---|---|
packages/*/src/**/*.ts (non-test) | API/Code | api |
packages/html/**, packages/react/** (UI) | UI Components | component, aria |
site/**/*.md, **/README.md, **/CLAUDE.md | Documentation | docs |
site/**/reference/*.mdx | API Reference | api-reference |
packages/*/src/**/*.test.ts | Tests | General review |
.claude/** | Agent Config | General review |
Config files (.json, .config.*) | Configuration | General review |
Report detected categories before proceeding:
Detected changes: [API/Code], [Documentation], [UI Components], etc.
For deeper domain-specific review, load the relevant skill:
| Category | Load Skill | For Deeper Review |
|---|---|---|
| API/Code | api | api/review/workflow.md |
| UI Components | component | component/review/workflow.md |
| UI Components | aria | aria/review/workflow.md |
| Documentation | docs | docs/review/workflow.md |
Skip this step for quick reviews using the inline checklists below.
Based on detected categories, load the relevant skill's review checklist:
| Category | Load Checklist |
|---|---|
| API/Code | api/review/checklist.md |
| UI Components | component/review/checklist.md |
| Accessibility | aria/review/checklist.md |
| Documentation | docs/review/workflow.md |
For test changes, apply these checks:
act → assert pattern<module>.test.tsdescribe() uses exact exported namevi.fn() for mockstests/ directory next to implementationIn addition to skill-based checks, review for:
Structure your review as:
## Change Summary
[1-2 sentences describing what changed]
## Detected Categories
- [x] API/Code changes
- [ ] UI Component changes
- [x] Documentation changes
- [ ] Test changes
## Findings
### [SEVERITY] Issue title
**What:** Brief description
**Where:** `path/to/file.ts:42`
**Why:** Impact on users/developers
**Fix:** Concrete suggestion
### [SEVERITY] Another issue...
## Recommendations
[Prioritized list of suggested improvements]
Severity Levels:
| Level | Meaning | Action |
|---|---|---|
CRITICAL | Breaks functionality, type safety, or a11y | Must fix before merge |
MAJOR | Violates core principles, hurts DX | Should fix |
MINOR | Suboptimal but workable | Consider fixing |
NIT | Polish, style preferences | Optional |
Think deeply about the implications of the changes here and proposed.
ONLY CREATE A SUMMARY. DO NOT WRITE ANY CODE.