Loading...
Loading...
Found 1,236 Skills
Generate a visual diff review page (ArchitectureGrid for impacted modules + CodeDiff for hunks + Callouts for risks) from a git range, PR URL, or pasted diff. Use whenever the user asks for a PR review, diff summary, change impact analysis, or pastes `git diff` output. Requires the `hyperscribe` skill (renderer engine).
When to ship vs not ship. The single ship gate, six auto-decision principles for plan reviews, and the Confusion Protocol for when to stop and ask.
You are a **Jira Workflow Steward**, the delivery disciplinarian who refuses anonymous code. If a change cannot be traced from Jira to branch to commit to pull request to release, you treat the wor...
Use this for {{FRAMEWORK}} components, pages, hooks, forms, and frontend refactors that should follow Panapps coding standards and review checklist.
Fix only small, high-certainty OpenClaw bugs from a pasted issue/PR list after deep code review.
Read open review comments and resolve them by making code fixes
Patterns and conventions for creating a good PR
Run a read-only, fresh-context branch-diff code review and report findings. Use when running /review-code, before finishing issue work, or when a local review gate should inspect committed, staged, unstaged, and untracked changes without mutating code or GitHub state.
Use to review uncommitted changes and recent commits in the working tree. Dispatches 8 specialized review agents in parallel and returns a consolidated report
Backseat gaming mode for coding — you can see exactly what's wrong and tell the user precisely what to do, but you never touch the code yourself. The user implements everything. Persistent, no exit. Activate with /backseat. Use when the user says /backseat, "coach me but don't code for me", "guide me while I implement", or wants to do the coding themselves with guidance.
Manage Harness Code pull requests via MCP. List, create, update, and merge PRs; add reviewers and submit review decisions (approve / request changes); post, update, and delete comments; read the discussion timeline; and check CI status. Use when asked to open a PR, merge a PR, approve a PR, leave a code review comment, request changes, assign reviewers, or inspect PR checks and activity. Trigger phrases: pull request, PR review, merge PR, approve PR, request changes, add reviewer, PR comments, PR checks, PR activity, code review.
Submit a code review to GitHub via the GitHub API. Use this as the final step in a code review pipeline to post review findings to a PR.