Flywheel Scan Issues
Goal
Find meaningful engineering issues from source code and create a bounded number of actionable issues.
Workflow
- •Read
.github/FLYWHEEL.mdand.github/workflows/scan.yml. - •Scan only the target directory and prioritize likely defect signals:
- •unsafe patterns
- •missing error handling
- •brittle logic
- •obvious test gaps
- •Read open issues first and skip duplicates by title/intent.
- •Generate a stable dedup fingerprint per issue and include it in issue body:
- •Format:
[fingerprint:<value>] - •Value should be derived from file path + issue type + normalized symptom key.
- •Format:
- •Create at most
MAX_ISSUESissues for this run. - •Apply one priority label (
p0/p1/p2/p3) and one type label when available. - •Keep issue body concise and reproducible (location, risk, expected outcome).
Safety Rules
- •Never create low-signal spam issues.
- •Never exceed
MAX_ISSUES. - •Never modify repository code in scan mode.
Output Checklist
- •Scanned paths
- •Created issue numbers
- •Deduplication summary