bugfix-councilworkflow★0
levelupadmin/LevelUp-Main-App ↗What it does
Adversarially red-team a bug fix across blast radius and security
Best for
Preventing subtle multi-platform regressions before a bug fix ships by exhaustively probing blast radius
Inputs
- · fix description (string)
- · touched files (optional array)
- · platform scope (optional string)
Outputs
- · multi-lens review verdict {root-cause, blast-radius, alternatives, security}
- · confirmed findings array {issue, severity, evidence, recommendation}
Requires
- · git (read diff, show HEAD)
- · agent orchestration (parallel lenses)
- · Glob/Read for touched file inspection
Preconditions
- · git repo initialized
- · fix staged or committed
- · touched files readable
Failure modes
- · Blast radius on secondary platform missed (e.g., Android WKWebView overlooked)
- · Root-cause masking symptom not caught
- · Alternative fix discovery exhausted but wrong choice selected
Trust signals
- · 2-phase Review → Verdict
- · 4 adversarial lenses (root-cause, blast-radius, alternatives, security)
- · Blast-radius lens mandated as THE MOST IMPORTANT
- · Platform-specific analysis (desktop web, Android System WebView, Android Chrome, iOS WKWebView, server, DB)