'code-review' 검색 결과

Cut a Han release: update CHANGELOG.md with the changes since the last release, bump and tag every plugin that changed as {plugin-name}--v{version} so a version-constrained dependency can resolve, and publish a GitHub release crediting every merged pull request and closed issue to the people behind it. Use when releasing, cutting a release, shipping a new Han version, publishing release notes, or tagging a version. Always stops for approval before creating any tag, because a pushed tag is never moved. Requires the gh CLI, jq, the claude CLI, and a clean git checkout. This is a repository-maintenance skill for the Han repo itself, not a general review or PR skill — use code-review for local review, post-code-review-to-pr to post a PR review, and update-pr-description for PR bodies.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Restructure existing code without changing its behavior, through a test-gated refactoring loop: a named target, a green suite over that target before any edit, a planned sequence of small named refactorings, and the full suite re-run after every step. Use when the user wants to refactor, restructure, clean up, simplify, or improve the design of existing code, or to apply refactoring recommendations from a code-review or architectural-analysis report. This skill changes code; it does not review code (use code-review), assess architecture (use architectural-analysis), plan a multi-module restructure before executing it (use plan-a-change), map domain boundaries before restructuring along them (use ddd-analysis), or build new behavior test-first (use tdd). Do not use it on code inside an active tdd loop; the refactor step of tdd owns that cleanup. Runs its planned sequence to completion without pausing for review; to review each named refactoring as it lands, use pairing.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Code review practices with technical rigor and verification gates. Use for receiving feedback, requesting code-reviewer subagent reviews, or preventing false completion claims in pull requests.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Perform thorough code reviews with actionable, prioritized feedback. Use when a user asks to review code, check code quality, find bugs, review a pull request, audit code for issues, or get feedback on implementation. Covers correctness, security, performance, readability, and best practices across languages.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

The art of reviewing code that improves both the codebase and the developer - sharing knowledge, maintaining standards, and building cultureUse when "code review, PR review, pull request, merge request, review comments, LGTM, review feedback, approve PR, request changes, review checklist, code quality, review standards, code-review, pull-request, PR, quality, standards, feedback, collaboration, mentoring" mentioned.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Code review specialist for quality standards, design patterns, security review, and constructive feedbackUse when "code review, pull request, PR review, code quality, refactor, technical debt, design pattern, best practice, code-review, quality, patterns, security, refactoring, best-practices, pull-request, review, ml-memory" mentioned.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Comprehensive GitHub code review with AI-powered swarm coordination

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Comprehensive GitHub code review with AI-powered swarm coordination

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Delegate code review to a subagent running a specific model. Use ONLY when user explicitly names a model to review changes ("review with opus", "use sonnet to review", "review with gemini"). The root agent reconstructs changes from conversation history and spawns a subagent with the code-review skill using the specified model. Do NOT use for general code review (use code-review skill instead), for reviewing PRs from git history, or when no model is specified by the user.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Comprehensive GitHub code review with AI-powered swarm coordination

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Code review knowledge base: quality, security (OWASP Top 10), error-handling, performance, and test-coverage checklists with severity-ranked output format. Use when reviewing code changes, PRs, or before commits. Loaded automatically by the code-reviewer agent.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Reviews Python boundaries, typing, error handling, tests, dependencies, and supported-version idioms against the target project's contracts and active tools. Loaded by dh:code-reviewer for Python source; uses Python-engineering standards when available and retains standalone checks otherwise.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Reviews browser-rendered HTML, CSS, JSX, TSX, JavaScript, and TypeScript for accessibility, XSS, forms, focus, rendering performance, styles, and lifecycle cleanup. Loaded by dh:code-reviewer when source or framework entrypoints establish frontend execution; composes with TypeScript checks.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Provides TypeScript-specific code review patterns covering strict mode, ESM, type safety, branded types, discriminated unions, async patterns, runtime safety, and common anti-patterns. Activates on detection of tsconfig.json, *.ts, or *.tsx files during code review — loaded automatically by dh:code-reviewer.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Reviews skill, agent, and plugin artifacts against their intended consumer's schema and runtime contract. Loaded by dh:code-reviewer for SKILL.md, agent definitions, or plugin manifests; checks discovery, frontmatter, triggers, tools, context cost, bundled references, and caller handoffs.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

对抗性代码评审：代码质量 / 可维护性 / 时序风险 / 综合友好度 / MAS 对齐度。默认 ruthless 模式，找 EVERY flaw。触发场景：(1) RTL lint 后；(2) 显式 /bb-code-review。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Process and act on code review feedback. Use when receiving review results.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Design AI-powered code review systems. TRIGGERS - Use when user needs help with ai-code-review-system related tasks.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when legacy prompts or older framework flows reference `code-reviewer` and you need the modern runtime to resolve that capability cleanly.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when legacy prompts or older framework flows reference `code-review-expert` and you need the modern runtime to resolve that capability cleanly.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

中文 review 沟通参考——话术模板、分级标注（必须修复/建议修改/仅供参考）、国内团队常见反模式应对。仅在用户显式 /chinese-code-review 时调用，不要根据上下文自动触发。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.