636건 · 관련도순
Review code changes or a repository for actionable bugs by tracing how components interact. Findings explain reachable triggers, incorrect behavior, consequences, and checked counterarguments. Correctness is the default focus; performance and security can also be selected.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review game code for architecture, coding standards, testability, and performance concerns. Get findings tied to specific code, checks against recorded design decisions, and a report separating required fixes from optional improvements.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Explore relationships between functions and files using a prebuilt code graph, a map of code dependencies. Trace bugs, inspect callers and execution paths, and assess the impact of refactoring or proposed changes.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review code changes for security, performance, correctness, and maintainability. Get findings tied to files and lines, severity ratings, practical suggestions with code examples, and a recommendation to approve, request changes, or discuss further.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Organizes a code review by giving a reviewer subagent the requirements, a change summary, and the relevant Git commits. It helps check completed work and handle findings by severity before continuing or merging.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Comprehensive GitHub code review with AI-powered swarm coordination
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
[omh] Pull request or changes to vet: bug-first review with evidence. Use when the user says: code-review, review, audit, find bugs, release gate, claim audit, evidence audit, README claim.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when receiving code review feedback (especially if unclear or technically questionable), when completing tasks or major features requiring review before proceeding, or before making any completion/success claims. Covers three practices - receiving feedback with technical rigor over performative agreement, requesting reviews via code-reviewer subagent, and verification gates requiring evidence before any status claims. Essential for subagent-driven development, pull requests, and preventing false completion claims.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Provides comprehensive code review guidance for React 19, Vue 3, Angular 17+, Svelte 5, Rust, TypeScript, Java, Java 8, PHP, Ruby, Rails, Python, Django, FastAPI, Go, C#/.NET, Kotlin, Swift, Dart, Flutter, NestJS, C/C++, Zig, CSS/Less/Sass, Qt, and more. Covers architecture review, performance review, security audit, code quality anti-patterns, and common bugs across all ecosystems. Use when: reviewing pull requests, conducting PR reviews, code review, reviewing code changes, establishing review standards, mentoring developers, architecture reviews, security audits, performance reviews, checking code quality, finding bugs, giving feedback on code.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Performs a structured five-stage code review covering requirements compliance, correctness, code quality, testing, and security/performance. Each stage uses targeted checklists and categorized feedback (Blocker/Major/Minor/Nit) with actionable suggestions and rationale. Use when the user asks for code review, PR feedback, pull request review, or wants their code checked for bugs, style issues, or vulnerabilities — triggered by phrases like "review my code", "check this PR", "review my changes", "pull request review", or "code feedback".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Simplify code that works — remove speculative abstraction, dead flexibility, and needless indirection while keeping behaviour identical and verified. Use when a feature has just landed ('now simplify it'), when AI-generated code arrives over-engineered, when a file has grown hard to follow, or as the cleanup pass before review. Produces a smaller, flatter version with identical behaviour, plus a ledger of what was removed and why it was safe. For finding bugs use code-review-checklist / ai-code-review — this skill assumes it works and makes it simple.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Review AI-authored code for its characteristic failure modes — plausible-but-wrong logic, hallucinated APIs, over-engineering, dead scaffolding, and silent security shortcuts. Use when reviewing an AI-generated or heavily AI-assisted PR, when AI-written code keeps shipping subtle bugs, or when setting review standards for a team using coding agents. Produces a focused review with AI-specific findings, verification steps per risk class, and a team checklist for AI-authored changes. For general PR review use code-review-checklist — this skill covers what that one assumes a human wouldn't do.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Closeout pass on a finished substantive change — sequence refactor-clean (shape), code-review (diff), and write-docs (docs) so all three run, in the order where each feeds the next. Use after implementing a slice or feature and before calling it done or committing; when the user asks for a final review, a cleanup-and-document pass, or to "review everything." For a diff-only audit, reach code-review directly.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Code review automation for TypeScript, JavaScript, Python, Go, Swift, and Kotlin. Analyzes PRs for complexity, risk, SOLID violations, and code smells. Use when reviewing PRs, analyzing code quality, or generating review checklists.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Comprehensive GitHub code review with AI-powered swarm coordination
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use after gsd-code-review has written REVIEW.md, when you want its Critical and Warning findings fixed. Spawns the fixer agent, commits each fix atomically and writes REVIEW-FIX.md (--all, --auto to iterate).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use after a phase's code is written, or when the user asks to review changed files for bugs, security issues, or quality. Spawns the gsd-code-reviewer agent at quick, standard, or deep depth and writes the phase REVIEW.md.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Comprehensive GitHub code review with AI-powered swarm coordination
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Comprehensive GitHub code review with AI-powered swarm coordination
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use code-review-graph for local-first CLI/MCP code knowledge graphs, graph-backed code review, structural search, and repository-analysis integrations.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run a full pull request review and post review comments directly to the current branch's GitHub PR. Requires the gh CLI to be installed and a PR to already exist for the current branch. Use when you want review feedback posted to GitHub as PR comments. For local code review without posting to GitHub, use code-review instead. Does not write or update PR descriptions — use update-pr-description for that.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Evidence-based investigation of issues, bugs, API calls, integrations, and other aspects of software development that need a deep dive to find the root cause and solutions. Use when you need to debug, troubleshoot, diagnose, or figure out why something is broken. Does not review code for quality or style — use code-review for auditing changes or post-code-review-to-pr for posting review feedback to GitHub. Does not assess architectural health or structural risk — use architectural-analysis for architectural concerns. Does not research open-ended options, prior art, or how something works when nothing is broken — use research for that. Does not plan the structural change a root cause calls for — use plan-a-change. Does not map bounded contexts or domain boundaries — use ddd-analysis. Does not capture feedback on Han's own skills — use han-feedback for that.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run a comprehensive code review on local source files. Use this skill when the user asks to review, audit, inspect, evaluate, or check code, even if they never use the word "review." Does not post comments to GitHub pull requests — use post-code-review-to-pr for that. Does not analyze architectural structure or module boundaries — use architectural-analysis for that. Does not explain code or a PR to build understanding before reviewing — use code-overview for a written overview, or code-walkthrough to be paced through it one step at a time. Does not map bounded contexts or domain boundaries — use ddd-analysis for that. Does not capture feedback on Han's own skills — use han-feedback for that.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Produces a human-readable, progressive-disclosure overview of unfamiliar code or a pull request's changes — why it exists (the real problem it solves or goal it serves for the business or a user), and from there what it does, how it flows, and where to start — so you can get up to speed before working on or reviewing it. Use when you want to understand, get oriented in, make sense of, explain, or get up to speed on a chunk of code, a file, a directory, a symbol, or a PR's changes. Writes the overview to a scratch file and changes no code. Does not review code quality or raise findings — use code-review for auditing changes or post-code-review-to-pr for posting them. Does not produce durable feature or system documentation — use project-documentation. Does not assess architecture or structural risk — use architectural-analysis. Does not diagnose bugs or root-cause failures — use investigate. Does not pace a person through the code one step at a time in conversation — use code-walkthrough.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.