644건 · 관련도순
Debug pipeline: investigates a bug, diagnoses root cause, writes failing tests, implements fix via TDD, and reviews the result. Orchestrates bug-investigator -> bug-fixer -> code-reviewer.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Lightweight build: explore → plan → approve → implement in a single Opus context, no sub-agent fan-out. Verifies build + tests, optionally commits, and offers a separate /code-review pass at the end. Use by default for everyday features; reach for /claude-setup:build only when the work needs parallel fan-out or exceeds one context.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Lightweight refactor: audit → plan → approve → implement in a single Opus context, no sub-agent fan-out. Behavior preservation is the goal — verifies tests still pass, optionally commits, and offers a separate /code-review pass at the end. Use by default; reach for /refactor only when the cleanup needs parallel fan-out or exceeds one context.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Refactoring pipeline: analyzes a target file or directory for code quality issues, plans safe incremental improvements, optionally writes tests first as a safety net, implements the changes, and reviews the result. Orchestrates refactor-planner → (test-writer) → parallel-task-orchestrator → code-reviewer.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Lightweight refactor: audit → plan → approve → implement in a single Opus context, no sub-agent fan-out. Behavior preservation is the goal — verifies tests still pass, optionally commits, and offers a separate /code-review pass at the end. Use by default; reach for /claude-setup:refactor only when the cleanup needs parallel fan-out or exceeds one context.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
代码审查师（科迪 Cody）——专注于从安全性、性能、正确性和可维护性四个维度对代码变更进行结构化审查，输出安全漏洞、性能问题、正确性缺陷和可维护性隐患的详细报告。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Comprehensive code review checklist and methodology. Use when reviewing PRs, conducting code audits, or assessing code quality. Keywords: review, PR, code review, audit, assess, quality, check
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Code review guidelines covering code quality, security, and best practices.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
REQUIRED before declaring a task done when the diff touches user input, SQL, shell, auth, credentials, file paths, serialization, crypto, network endpoints, data deletion, or dependency surface. Judge by that surface, not the task label — research/experimental/local-only code with none of it can skip this. Walks OWASP/ASVS/MITRE questions the compiler and the test suite won't catch. Pair with `rafter run` on the same diff. When the diff has that surface, marking it complete without both has been under-delivered — do not claim done.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
差分、PR、選択範囲、指定ファイルを多角的にレビューし、既定は read-only、明示指示があれば critic review 後に修正と検証まで行う。日常コードレビューの入口で、`fix` 指定で Fix now / Guard now / Block に分けて最小修正・同根 Sweep・検証まで閉じる
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
差分、PR、選択範囲、指定ファイルをセキュリティ観点で read-only レビューし、rubber duck / critic review で確認してから高信頼の脆弱性を報告する
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Take one new feature slice from idea to reviewed, committed code in a single guided pass — scope it into the smallest shippable slice, build it test-first with strict TDD, review and fix the diff, then commit it. Chains slice → test-driven-development → the built-in /code-review → git-commit. Not for reviewing an existing PR, upgrades, or open-ended design questions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Review code changes for security, performance, and correctness. Trigger with a PR URL or diff, "review this before I merge", "is this code safe?", or when checking a change for N+1 queries, injection risks, missing edge cases, or error handling gaps.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Review code for quality, security, and performance with comprehensive feedback.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Claude-native review of code for quality, structure, naming, and maintainability (no external AI). Use when reviewing a file or diff for code quality before committing. Trigger on "review this code", "code review", "is this well-written". For security, use /security-verify; for companion-AI review, use /review.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Dispatch reviews to external companion AIs (Codex, Gemini, Claude) for an independent second opinion on code changes, PR readiness, doc completeness, architecture, or implementation status. Use when you want a fresh-eyes review beyond Claude-native. Trigger on "get a second opinion", "companion review", "review my changes", "review the PR". For Claude-only quality checks use /code-review.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Performs critical code reviews using REVIEW.md guidelines. Evaluates code quality, architecture, testing, and domain-specific concerns (legal faithfulness, cross-law references, engine safety). Use after completing significant code changes or before merging.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Structured code review discipline: correctness, design, readability, and security checks with actionable feedback. Use when reviewing diffs, PRs, or code snippets before merge or after writing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Professional code review craft: review strategy, feedback that lands, reviewer efficiency, and team review culture. Use when reviewing code or improving a team's review process.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.