Structured code review of git changes with senior engineer rigor. Checks SOLID violations, security risks, race conditions, error handling, performance, boundary bugs, and removal candidates. Outputs severity-classified findings (P0–P3) with actionable fixes. Don't use it for general coding tasks, non-git file editing, or writing new code from scratch.

glfruit0

コード品質

Sentry Release Triage

Use when a web app or service has Sentry installed and the task is to verify release readiness, source map correctness, environment wiring, or basic issue-triage hygiene before or after shipping. Inventories SDK setup, config files, release markers, and error-boundary coverage, then writes a focused triage plan.

gmackie0

コード品質

Task Code Review Flow Skill

Automated code review skill operating in two modes: (1) Standalone — find PR, run review, list BLOCKERs and ask user for approval before fixing; (2) Embedded — called by task-implementation-flow at Phase 8, auto-fixes all BLOCKERs without asking. Uses 3 review agents + 1 tooling runner (diff-only, token-efficient). Review is issue-scoped and validates only dimensions justified by the Jira task plus the PR diff. Supports all Jira formats (key, URL) and can be triggered standalone or embedded.

gmass0n0

コード品質

Verify

Post-implementation verification skill. Delegates to the implementation-verifier agent for build, test, lint, diff review, and readability checks. Enforces the Iron Law: no completion claims without fresh verification evidence. Invoke with `/verify` after /execute-plan completes.

CityBear30

コード品質

Receiving Code Review

Use when receiving code review feedback, before implementing suggestions — especially if feedback seems unclear or technically questionable. Requires technical rigor and verification, not performative agreement or blind implementation. Cross-cutting skill — invoke whenever review feedback arrives.

CityBear30

コード品質

Cycle Doc Planner

Use before any implementation work to create a bounded cycle document (~3 hours scope). Locks scope, lists all file changes, defines verification steps. Required for bug fixes, features, and refactoring.

cjairm0

コード品質

Verification Before Completion

Must run verification commands before claiming done. Evidence before claims.

CiuTheDEV0

コード品質

Fix

Fix a bug or implement a feature with verified before/after evidence

cjbest0

コード品質 Skills | Skills Pool