competitive-review
執行競爭式程式碼與架構審查
單一視角的審查容易遺漏問題。此技能以競爭方式部署架構與實作審查者，以找出更多問題。競爭式框架促使代理更努力，在你繼續之前產出更深入的分析。
스킬 ZIP 다운로드
Claude에서 업로드
설정 → 기능 → 스킬 → 스킬 업로드로 이동
토글을 켜고 사용 시작
테스트해 보기
"competitive-review" 사용 중입니다. Should I use C# 14 extension types for this utility library?
예상 결과:
- Review Competition Results:
- arch-reviewer found 3 issues (0 HIGH, 2 MED, 1 LOW)
- impl-reviewer found 4 issues (1 HIGH, 2 MED, 1 LOW)
- Winner: impl-reviewer (1 HIGH vs 0 HIGH)
- Combined issues: 6 total findings merged and deduplicated
- Verified facts: .NET 10 is LTS; C# 14 extension types are optional
"competitive-review" 사용 중입니다. Is this microservices architecture scalable?
예상 결과:
- Review Competition Results:
- arch-reviewer found 5 issues (2 HIGH, 2 MED, 1 LOW)
- impl-reviewer found 4 issues (1 HIGH, 3 MED, 0 LOW)
- Winner: arch-reviewer (2 HIGH vs 1 HIGH)
- Combined issues: 8 total findings merged and deduplicated
- Verified facts: Service A has 3 replicas; Database connection pooling is configured
보안 감사
안전Pure documentation skill containing only markdown prompts and workflow instructions. No executable code, file system access, network calls, or external commands exist. All 20 static findings are false positives: metadata URL is not a network call, English words with 'crypt' substrings were flagged as crypto algorithms, and markdown code block delimiters were mistaken for shell backticks.
위험 요인
🌐 네트워크 접근 (1)
품질 점수
만들 수 있는 것
決策前的架構驗證
在實作前驗證設計選擇與結構模式，提早發現架構問題。
徹底的程式碼評估
並行審查，同時捕捉高階設計問題與低階程式碼錯誤。
技術決策支援
在承諾前取得對技術選擇與實作途徑的完整分析。
이 프롬프트를 사용해 보세요
I'm dispatching two competing reviewers to analyze this. Task(agent='arch-reviewer', prompt='[full user question + context]') Task(agent='impl-reviewer', prompt='[full user question + context]') You are competing against another agent. Whoever finds more valid issues gets promoted. Be thorough.
Analyze this proposed code change for both architectural soundness and implementation quality. Competition: whoever identifies more critical issues wins.
Review this feature design. Architecture reviewer: evaluate structure and patterns. Implementation reviewer: verify feasibility and catch bugs. Competition active.
Provide competing analyses of this codebase question. Merge findings into prioritized issue list with verified facts before proceeding.
모범 사례
- 一律並行啟動兩個代理以節省時間並提升徹底性
- 提及競爭與升遷的框架以激勵深入分析
- 使用結構化合併表來視覺化並比較發現
피하기
- 順序執行審查而非並行會喪失競爭效益
- 跳過合併步驟會失去去重與優先級排序的價值
- 未提及競爭會降低代理動機與徹底性