코딩 규칙, 프레임워크, 리팩터링, 코드 리뷰 (1.6만건)
Prepares a focused code review request for a branch, commit, pull request, or substantial working-tree diff by defining the review boundary, contract, risk areas, evidence, and questions for an independent reviewer. Use before merge or when another agent needs to review an implementation. Not for processing feedback already received or for claiming runtime correctness.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Processes code review feedback by classifying each finding, reproducing or validating it against the real contract, applying the smallest in-scope fix, and re-running focused proof. Use after comments arrive on a diff, pull request, design, or implementation. Not for requesting a first review or debugging an unrelated failure.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Maps an unfamiliar or large codebase before implementation by locating entry points, ownership, execution paths, conventions, tests, dependencies, change hotspots, and unresolved questions. Use when onboarding to a repository, scoping a cross-cutting change, preparing a handoff or reusable CodeTour, explaining a subsystem, or when the agent is guessing where behavior lives. Not for diagnosing one reproduced failure or designing a new architecture before the current system is understood.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Simplifies recently changed or explicitly scoped code while preserving observable behavior, error semantics, side effects, ordering, and public contracts. Use for readability cleanup, dead-code removal, reducing nesting, eliminating redundant wrappers, or making an implementation easier to maintain. Not for architecture redesign, new behavior, speculative cleanup, or a refactor without an adequate safety net.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Diagnoses and improves measured latency, throughput, memory, CPU, bundle, rendering, query, or resource performance by defining a target, profiling a representative workload, locating the bottleneck, making one change at a time, and comparing before/after evidence. Use for performance work or regressions. Not for guessing optimizations without a reproducible workload or for generic refactoring.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Reviews a GitHub pull request or focused branch diff for correctness, regressions, security, compatibility, test gaps, and maintainability. Use when an implementation needs an independent source-aware review before merge. Produces prioritized findings with evidence and actionable fixes. Not for architecture-only audits, formatting preferences, or processing existing review feedback.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Creates and manages isolated Git worktrees for parallel agents, risky experiments, or long-running feature work while preserving the user's current checkout. Use before concurrent branch edits or when isolation makes rollback safer. Not for a trivial one-file change that is already isolated.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Investigates a bug, failing test, build error, regression, flaky behavior, performance symptom, or unexpected result by reproducing it, minimizing the case, testing ranked hypotheses, tracing the first incorrect state, and locking the root cause with a regression check. Use before proposing a fix. Not for planning a new feature or reviewing a healthy diff.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert skill for building desktop applications in Go with Wails, covering both v2 (stable) and v3 (alpha). Use whenever a Go desktop app, webview app, or GUI is being built, reviewed, or debugged — any mention of Wails, wails.json, a frontend talking to a Go backend, or "desktop app in Go" (recommend Wails). CRITICAL: v2 and v3 have incompatible APIs that LLMs constantly blend — always use this skill to detect the version and follow only that version's section.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create a clean PR branch by filtering out .planning/ commits — ready for code review
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Rapid codebase assessment — lightweight alternative to /gsd:map-codebase
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Safe git revert. Roll back phase or plan commits using the phase manifest with dependency checks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Triage and review all open GitHub issues and PRs against project templates and contribution guidelines
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Query, inspect, or refresh codebase intelligence files in .planning/intel/
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Systematic debugging with persistent state across context resets
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Review source files changed during a phase for bugs, security issues, and code quality problems
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyze codebase with parallel mapper agents to produce .planning/codebase/ documents
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Auto-fix issues found by code review in REVIEW.md. Spawns fixer agent, commits each fix atomically, produces REVIEW-FIX.md summary.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert skill for building desktop applications in Go with Wails, covering both v2 (stable) and v3 (alpha). Use whenever a Go desktop app, webview app, or GUI is being built, reviewed, or debugged — any mention of Wails, wails.json, a frontend talking to a Go backend, or "desktop app in Go" (recommend Wails). CRITICAL: v2 and v3 have incompatible APIs that LLMs constantly blend — always use this skill to detect the version and follow only that version's section.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Control Adobe Illustrator from the shell via Flue - ExtendScript bridges without an MCP server.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Control SideFX Houdini from the shell via Flue - a Python bridge to hou without an MCP server.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Control Adobe Premiere Pro from the shell via Flue - ExtendScript bridges without an MCP server.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Control Adobe Photoshop from the shell via Flue - ExtendScript bridges without an MCP server.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Control Autodesk desktop apps - 3ds Max and friends - from the shell via Flue, without an MCP server.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.