insight-challenge

# Insight Challenge Adversarial review of code quality findings. Challenges insights with counter-evidence, verifies claims against source code, and produces structured verdicts. **适用场景**: 当需要对代码审查、质量分析、或架构评估中的发现进行对抗性验证时使用。 ## Architecture ``` ┌─────────────────────────────────────────────────────────────┐ │ Insight Challenge (SKILL.md) — Adversarial Review │ │ → Parse finding → Read source → Challenge → Verdict │ └───────────────��─────────────────────────────────────────────┘ │ ┌──────────┬───────────┼───────────┬──────────┐ ↓ ↓ ↓ ↓ │ ┌────────┐ ┌────────┐ ┌────────┐ ┌────────┐ │ │Phase 1 │ │Phase 2 │ │Phase 3 │ │Phase 4 │ │ │ Parse │ │ Source │ │Challenge│ │Verdict │ │ │Finding │ │ Review │ │Analysis │ │Report │ │ └───┬────┘ └───┬────┘ └───┬────┘ └───┬────┘ │ │ │ │ │ │ finding source counter- structured │ parsed code evidence verdict │ ``` ## Key Design Principles 1. **Adversarial by Default**: Assume findings may be incorrect; seek counter-evidence first 2. **Source-Code Anchored**: All claims must be verified against actual code, not assumptions 3. **Structured Output**: Verdicts follow a fixed schema for downstream consumption 4. **Fair Challenge**: If evidence supports the finding, confirm it; don't manufacture doubt 5. **Transparent Reasoning**: Show the chain of evide...