ubs

<!-- TOC: Core Insight | THE EXACT PROMPT | Quick Reference | When to Use | Critical Rules | Suppression | Triage | Troubleshooting | AI Validation | References --> # Using UBS for Code Review > **Core Insight:** UBS catches what compiles but crashes — null derefs, missing await, resource leaks, security holes. It has many false positives; triage is essential, not optional. ## The Golden Rule ``` ubs <changed-files> before every commit. Exit 0 = safe to proceed. Exit 1 = triage findings. Exit 2 = run `ubs doctor --fix`. ``` --- ## THE EXACT PROMPT — Fix-Verify Loop ``` 1. Scan: Run UBS on changed files ubs --staged # Staged files (<1s) ubs --diff # Unstaged changes vs HEAD ubs file.ts file2.py # Specific files 2. Triage each finding: Real bug? → Fix root cause (not symptom) False positive? → // ubs:ignore — [why it's safe] 3. Re-run until exit 0 ubs --staged 4. Commit when clean ``` ### Why This Workflow Works - **`--staged` is fast** — Scans only what you're committing - **Fix root cause** — Masking symptoms creates debt - **Exit 0 gate** — Clean scan = confidence to commit - **Justification required** — Every `ubs:ignore` must explain why --- ## Quick Reference ```bash # Core workflow ubs --staged # Staged files only (<1s) ubs --diff # Working tree changes vs HEAD ubs . # Full project scan # Language-specific...