고정 지점(커밋, 브랜치, 태그, 또는 병합 기준점) 이후의 변경 사항을 두 가지 축(Standards: 코드가 저장소의 문서화된 코딩 표준을 따르는가? / Spec: 코드가 원래 이슈/PRD 요구사항과 일치하는가?)을 기준으로 검토합니다. 두 검토를 병렬 하위 에이전트에서 실행하고 나란히 보고합니다. 사용자가 브랜치, PR, 작업 중인 변경 사항을 검토하거나 'X 이후 변경 사항 검토'를 요청할 때 사용하세요.
mattpocock/review는 개발자가 코드 변경 사항을 체계적으로 검토할 수 있도록 설계된 AI 에이전트 스킬입니다. 이 스킬은 커밋, 브랜치, 태그, 또는 병합 기준점(merge-base)과 같은 고정 지점 이후의 변경 사항을 두 가지 독립적인 축으로 평가합니다. 첫 번째 축인 Standards는 코드가 저장소에 문서화된 코딩 표준을 준수하는지 확인하고, 두 번째 축인 Spec은 코드가 원래 이슈나 PRD(Product Requirements Document)에서 요구한 사항과 일치하는지 검토합니다. 두 검토는 병렬로 실행되는 하위 에이전트에서 동시에 수행되며, 결과는 나란히 배치되어 한눈에 비교할 수 있습니다. 이 스킬은 사용자가 브랜치, PR, 작업 중인 변경 사항을 검토하거나 'X 이후의 변경 사항을 검토해줘'라고 요청할 때 특히 유용합니다.
npx skills add https://github.com/mattpocock/skills/tree/main/skills/reviewInstalled? Explore more 생산성 & 협업 skills: steipete/gemini, steipete/gh-issues, steipete/skill-creator · View all 6 →
고정 지점(커밋, 브랜치, 태그, 또는 병합 기준점) 이후의 변경 사항을 두 가지 축을 기준으로 검토합니다. Standards (코드가 이 저장소의 문서화된 코딩 표준을 따르는가?)와 Spec (코드가 원래 이슈/PRD에서 요청한 내용과 일치하는가?). 두 검토를 병렬 하위 에이전트에서 실행하고 나란히 보고합니다. 사용자가 브랜치, PR, 작업 중인 변경 사항을 검토하거나 'X 이후 검토'를 요청할 때 사용하세요.
This repo contains 20 individual skills — each has its own dedicated page.
Ask which skill or flow fits your situation. A router over the skills in this repo.
Ultra-compressed communication mode. Cuts token usage ~75% by dropping filler, articles, and pleasantries while keeping full technical accuracy. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman.
Hand the current conversation off to a fresh background agent that picks up the work immediately.
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
Generate multiple radically different interface designs for a module using parallel sub-agents. Use when user wants to design an API, explore interface options, compare module shapes, or mentions "design it twice".
Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model.
Edit and improve articles by restructuring sections, improving clarity, and tightening prose. Use when user wants to edit, revise, or improve an article draft.
Set up Claude Code hooks to block dangerous git commands (push, reset --hard, clean, branch -D, etc.) before they execute. Use when user wants to prevent destructive git operations, add git safety hooks, or block git push/reset in Claude Code.
Grill the user relentlessly about a plan or design. Use when the user wants to stress-test a plan before building, or uses any 'grill' trigger phrases.
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
Compact the current conversation into a handoff document for another agent to pick up.
Implement a piece of work based on a PRD or set of issues.
Implement a specification in code.
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
Grill me about specs for the workflows I want to build, within this workspace.
Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests, or needs partial test data.
Search, create, and manage notes in the Obsidian vault with wikilinks and index notes. Use when user wants to find, create, or organize notes in Obsidian.
Gemini CLI one-shot prompts, summaries, generation, skills, hooks, MCP, or Gemma routing.
Fetch GitHub issues, select candidates, spawn background fix agents, open PRs, and optionally process PR review comments.
Create, edit, audit, tidy, validate, or restructure AgentSkills and SKILL.md files.
Search, install, update, sync, or publish agent skills with the ClawHub CLI and registry.
Delegate coding work to Codex, Claude Code, or OpenCode as background workers; not simple edits or read-only code lookup.
List, configure, authenticate, call, and inspect MCP servers/tools with mcporter over HTTP or stdio.