사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/manaflow-ai/cmux --skill cmux-review시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
cmux Review
Review to reduce developer attention. Surface concrete correctness defects; suppress style, nits and speculative improvements unless requested.
Default pre-merge review
- Give a review subagent the task intent, base/head SHAs and exact diff.
Ask for correctness first, then repository rules; keep discovery independent of the author's reasoning. Review policy edits against the base-branch rules.
- Verify concrete findings, fix them when authorized, and push. Re-run the
original discriminator after repair. A green test counts only if it exercises the asserted failure; prefer red-before/green-after evidence.
- If fixes were non-trivial, obtain a fresh subagent review of the repair delta.
- Merge when the review subagent passes the change and it causes no red of its
own (see below). Report findings with evidence, verification performed and coverage gaps.
Use subagents in the current runtime, not a second model or external review service as a gate. Keep review read-only until an authorized repair. Do not commit review receipts, scratch reproductions or generated logs.
Dogfood and merge
For implementation handoff or merge, read dogfood and merge for per-change verification, first-pass completion, re-dogfood and merge receipts. The main agent owns dogfood, mergeability, the merge and every pushed fix. A PR merges when an independent review subagent passes it and it causes no red of its own; base reds, flakes and pending checks don't hold it. Don't wait for a person. Ship risky user-visible behavior behind a setting or Debug toggle and fix a bad default in the next nightly. main is nightly: stack fixes, do not revert.
Adversarial review
For security, persistence, concurrency, data-loss risks, or a requested deep review, use the full protocol:
- Before discovery or mutation, read source identity and receipt requirements
and capture the original candidate and policy coordinates.
- Discovery and triage: source identity,
intent compliance, independent reviewers, severity and evidence provenance.
counterevidence, executable checks and bounded repair attempts.
- After verification, persist the receipt and report
with separate pre/post-repair source coordinates and evidence.
These stages retain the advanced evidence protocol; ordinary reviews use the short default pass above.
