ubs-workflow

Scan code with UBS, triage findings, and apply tested fixes before commits.

3|1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/burningportra/agent-flywheel-plugin --skill ubs-workflow-burningportra
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ubs-workflow
Source: https://github.com/burningportra/agent-flywheel-plugin/tree/main/skills/ubs-workflow
Command: npx skills add https://github.com/burningportra/agent-flywheel-plugin --skill ubs-workflow-burningportra

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code that compiles can still crash in production through null dereferences, missing awaits, resource leaks, and swallowed errors. This Skill provides a deterministic five-step workflow for scanning code with the Ultimate Bug Scanner (UBS), triaging real bugs from false positives, and applying verified fixes before every commit. ## Core Features & Use Cases - Structured Scan Workflow: Run staged, diff-based, or full-project scans with language-specific flags and JSON/SARIF output formats. - Triage Decision Tree: Classify findings by severity (blocks commit, blocks PR, discuss in PR) and distinguish real bugs from false positives using a deterministic decision tree. - Fix and Suppress Safely: Apply fixes with root cause analysis, test cases, and commit message templates, or suppress false positives with mandatory justification comments. - Use Case: After an AI assistant generates a TypeScript API handler, run ubs --staged --fail-on-warning to catch a missing await and an unparameterized SQL query, then follow the fix template to add tests and commit with finding references. ## Quick Start Ask the assistant to scan your staged changes with UBS, triage any findings by severity, and generate a fix plan with tests for each real bug.

Frequently Asked Questions about ubs-workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I scan staged files for bugs before a git commit?

Run `ubs --staged` to scan only staged files in under a second. Exit code 0 means it is safe to commit, exit code 1 means findings need triage, and exit code 2 means you should run `ubs doctor --fix` to repair the environment.

How do I suppress false positives in UBS scan results?

Add an inline suppression comment with a mandatory justification, such as `// ubs:ignore - validated by caller` for JS/TS/Go/Rust, `# ubs:ignore - reason` for Python, or `-- ubs:ignore - reason` for SQL. Suppressions without justification are considered bad practice.

Does UBS support scanning TypeScript and Rust projects?

Yes, UBS supports TypeScript, JavaScript, Rust, Go, Python, and other languages. Use language flags like `ubs --only=ts,tsx src/` or `ubs --only=rust src/` to scope scans, noting that `--only=js` excludes TypeScript files.

Why does UBS return exit code 2 and how do I fix it?

Exit code 2 indicates missing optional scanners or a degraded AST engine, often affecting JS/TS analysis. Run `ubs doctor` to diagnose the environment and `ubs doctor --fix` to automatically repair the installation.

How do I reduce noise from UBS on legacy codebases?

Use `ubs --skip=11,12` to skip TODO and debug categories, `--profile=loose` to skip minor nits, or `--comparison=baseline.json` to report only new issues relative to a baseline. You can also add test fixtures to `.ubsignore`.

Can UBS findings be exported to an issue tracker?

Yes, run `ubs scan --format bv | bv import --tag ubs-review` to convert findings into trackable beads in the bv issue tracker. This integrates code review findings into project management workflows.