ce-code-review은(는) 무엇을 하나요?
티어형 페르소나 에이전트, 신뢰도 기반 결과 필터링, 병합/중복 제거 파이프라인을 사용하는 구조화된 코드 리뷰입니다. 대화형 모드에서는 안전하고 검증된 수정 사항을 적용하고, 작업 트리가 깨끗할 때 커밋합니다(푸시하지 않음). mode:agent에서는 보고만 하고 호출자가 수정 사항을 적용합니다. PR 생성 전 코드 변경 사항을 검토할 때 사용하세요.
티어형 페르소나 에이전트, 신뢰도 기반 결과 필터링, 병합/중복 제거 파이프라인을 사용하는 구조화된 코드 리뷰 스킬입니다. 대화형 모드에서는 안전하고 검증된 수정 사항을 적용하고, 작업 트리가 깨끗할 때 커밋합니다(푸시하지 않음). mode:agent에서는 보고만 하고 호출자가 수정 사항을 적용합니다. PR 생성 전 코드 변경 사항을 검토할 때 사용하세요.
이 스킬은 여러 티어의 페르소나 에이전트를 활용하여 구조화된 코드 리뷰를 수행합니다. 각 에이전트가 독립적으로 코드를 검토하고, 신뢰도 임계값을 통과한 결과만 최종 리뷰에 포함됩니다. 중복 제거 및 병합 파이프라인을 통해 에이전트 간 중복 의견을 효과적으로 처리합니다. 대화형 모드에서는 안전한 수정 사항을 자동으로 적용 및 커밋하며(푸시는 하지 않음), mode:agent 모드에서는 리뷰 결과만 보고하여 호출자가 직접 수정하도록 합니다. 주로 PR 생성 전 코드 변경 사항을 검토하는 데 유용하며, 일관된 리뷰 품질과 효율적인 워크플로우를 제공합니다.
npx skills add https://github.com/everyinc/compound-engineering-plugin/tree/main/skills/ce-code-reviewInstalled? Explore more 생산성 & 협업 skills: steipete/gemini, steipete/gh-issues, steipete/skill-creator · View all 6 →
티어형 페르소나 에이전트, 신뢰도 기반 결과 필터링, 병합/중복 제거 파이프라인을 사용하는 구조화된 코드 리뷰입니다. 대화형 모드에서는 안전하고 검증된 수정 사항을 적용하고, 작업 트리가 깨끗할 때 커밋합니다(푸시하지 않음). mode:agent에서는 보고만 하고 호출자가 수정 사항을 적용합니다. PR 생성 전 코드 변경 사항을 검토할 때 사용하세요.
This repo contains 20 individual skills — each has its own dedicated page.
Build applications where agents are first-class citizens. Use this skill when designing autonomous agents, creating MCP tools, implementing self-modifying systems, or building apps where features are outcomes achieved by agents operating in a loop.
Run comprehensive agent-native architecture review with scored principles
Explore requirements and approaches through collaborative dialogue, then write a right-sized requirements document. Use when the user says "let's brainstorm", "what should we build", or "help me think through X", presents a vague or ambitious feature request, or seems unsure about scope or direction -- even without explicitly asking to brainstorm.
Clean up local branches whose remote tracking branch is gone. Use when the user says "clean up branches", "delete gone branches", "prune local branches", "clean gone", or wants to remove stale local branches that no longer exist on the remote. Also handles removing associated worktrees for branches that have them.
Create a git commit with a clear, value-communicating message. Use when the user says "commit", "commit this", "save my changes", "create a commit", or wants to commit staged or unstaged work. Produces well-structured commit messages that follow repo conventions when they exist, and defaults to conventional commit format otherwise.
Commit, push, and open a PR with an adaptive, value-first description that scales in depth with the change. Use when the user says "commit and PR", "ship this", "create a PR", or "open a pull request". Also handles description-only flows ("write a PR description", "rewrite the PR body", "describe this PR") without committing or pushing.
Document a recently solved problem to compound your team's knowledge or CONCEPTS.md, the project's shared domain vocabulary.
Refresh stale learning and pattern docs under docs/solutions/ by reviewing them against the current codebase, then updating, consolidating, or deleting drifted ones. Use when the user asks to "refresh my learnings", "audit docs/solutions/", "clean up stale learnings", or "consolidate overlapping docs", or when ce-compound flags an older doc as superseded. Do not trigger for general refactor, debugging, or code-review work unless the user has explicitly pointed at docs/solutions/.
Systematically find root causes and fix bugs. Use when debugging errors, investigating test failures, reproducing bugs from issue trackers (GitHub, Linear, Jira), or when stuck on a problem after failed fix attempts. Also use when the user says 'debug this', 'why is this failing', 'fix this bug', 'trace this error', or pastes stack traces, error messages, or issue references.
Capture a visual demo reel (GIF, terminal recording, screenshots) for PR descriptions. Use when shipping UI changes, CLI features, or any work with observable behavior that benefits from visual proof. Also use when asked to add a demo, record a GIF, screenshot a feature, show what changed visually, create a demo reel, capture evidence, add proof to a PR, or create a before/after comparison.
This skill should be used when writing Ruby and Rails code in DHH's distinctive 37signals style. It applies when writing Ruby code, Rails applications, creating models, controllers, or any Ruby file. Triggers on Ruby/Rails code generation, refactoring requests, code review, or when the user mentions DHH, 37signals, Basecamp, HEY, or Campfire style. Embodies REST purity, fat models, thin controllers, Current attributes, Hotwire patterns, and the "clarity over cleverness" philosophy.
Review requirements or plan documents using parallel persona agents that surface role-specific issues. Use when a requirements document or plan document exists and the user wants to improve it.
Build web interfaces with genuine design quality, not AI slop. Use for any frontend work - landing pages, web apps, dashboards, admin panels, components, interactive experiences. Activates for both greenfield builds and modifications to existing applications. Detects existing design systems and respects them. Covers composition, typography, color, motion, and copy. Verifies results via screenshots before declaring done.
This skill should be used when generating and editing images using the Gemini API (Nano Banana Pro). It applies when creating images from text prompts, editing existing images, applying style transfers, generating logos with text, creating stickers, product mockups, or any image generation/manipulation task. Supports text-to-image, image editing, multi-turn refinement, and composition from multiple reference images.
Generate and critically evaluate grounded ideas about a topic. Use when asking what to improve, requesting idea generation, exploring surprising directions, or wanting the AI to proactively suggest strong options before brainstorming one in depth. Triggers on phrases like 'what should I improve', 'give me ideas', 'ideate on X', 'surprise me', 'what would you change', or any request for AI-generated suggestions rather than refining the user's own idea.
Run metric-driven iterative optimization loops -- define a measurable goal, run parallel experiments, measure each against hard gates or LLM-as-judge scores, keep improvements, and converge on the best solution. Use when optimizing clustering quality, search relevance, build performance, prompt quality, or any measurable outcome that benefits from systematic experimentation.
Create structured plans for multi-step tasks -- software features, research workflows, events, study plans, or any goal that benefits from breakdown. Also deepens existing plans with interactive sub-agent review. Use when the user says 'plan this', 'create a plan', 'how should we build', 'break this down', or when a brainstorm doc is ready for planning. Use 'deepen the plan' or 'deepening pass' for the deepening flow. For exploratory requests, prefer ce-brainstorm first.
[BETA] Start the dev server, open the feature in a browser, and iterate on improvements together.
Generate a time-windowed pulse report on what users experienced and how the product performed - usage, quality, errors, signals worth investigating. Use when the user says 'run a pulse', 'show me the pulse', 'how are we doing', 'weekly recap', 'launch-day check', or passes a time window like '24h' or '7d'. Configures via .compound-engineering/config.local.yaml and saves reports to docs/pulse-reports/.
Publish, view, comment on, and edit markdown via Proof (proofeditor.ai) — create a shareable doc, read a shared doc, and make comment/suggestion/block edits over its API. Use when the user says "view this in proof", "share to proof", "publish to proof", or wants a shareable markdown surface for a spec, plan, or draft, including publish handoffs from ce-brainstorm, ce-ideate, or ce-plan. Do not trigger on "proof" meaning evidence, math proofs, proof-of-concept, or "proofread this".
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.