How do I install the Ubs skill?

Run npx skillmds@latest add lev-os/ubs in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ubs?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

lev-os (@lev-os) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Ubs by lev-os — Agent Skill

Name: Ubs
Rating: 4.2 (5 reviews)
Author: lev-os

Ubs

[WHAT] Static-analysis quality-gate wrapper around the external `ubs` CLI (Ultimate Bug Scanner). [HOW] Runs `ubs` on staged, diffed, or explicitly changed files with structured output, then uses the findings as a pre-commit or pre-review bug gate. [WHEN] Use before commit, during code review, when the user asks for bug scanning, or when a change needs a fast multi-language sanity pass. [WHY] Catches AI-agent bug patterns early without making UBS itself the project workflow router. Triggers: "ubs", "ultimate bug scanner", "bug scan", "static analysis", "quality gate", "scan for bugs", "pre-commit scan"

lev-os 22ff9d5 2.9 KB Updated Sep 10, 2026

File contents

UBS

Use ubs as a scoped gate. Keep the scope tight unless the user explicitly wants a full baseline scan.

Prerequisites

command -v ubs

If missing, stop and tell the user:

brew install dicklesworthstone/tap/ubs

Golden Rules

Prefer --staged, --diff, or explicit files over ubs ..
Use --format=json when you need machine-readable output.
Re-run after fixes to confirm the exit code is clean.
Treat UBS as a tool boundary; do not import its repo-level hooks as implicit Lev policy.

Fast Path

ubs --staged --format=json --ci

If you only changed a few files:

ubs path/to/file.ts path/to/other.py --format=json --ci

Core Commands

Narrow scans

ubs --staged --format=json --ci
ubs --diff --format=json --ci
ubs src/file.ts src/other.py --format=json --ci

Full or filtered scans

ubs . --format=json --ci
ubs --only=js,python . --format=json --ci
ubs --category=resource-lifecycle . --format=json --ci

Diagnostics

ubs doctor
ubs doctor --fix

Recommended Workflow

Before commit

ubs --staged --fail-on-warning --format=json --ci

During review

Scan only the touched files.
Inspect critical findings first.
Fix root causes, not symptoms.
Re-run the same narrow scan.

Output Handling

Focus on:

summary
findings[].file
findings[].line
findings[].severity
findings[].category
findings[].message

If the user wants GitHub or CI artifacts:

ubs . --format=sarif --ci
ubs . --report-json .ubs/latest.json --html-report .ubs/latest.html --ci

When Not To Use UBS

Do not default to UBS when:

the user wants architectural review rather than static findings
there are no changed files and no request for a baseline scan
another domain-specific checker is clearly more appropriate

Anti-Patterns

Running ubs . on every small edit
Ignoring critical findings without checking the code
Treating UBS findings as proof without context
Installing repo hooks or settings from the upstream repo without explicit user approval

Minimal Report Pattern

## UBS Findings
- Scope scanned:
- Critical:
- Warnings:
- Follow-up fixes:

Keep the summary in the active Lev artifact or review comment, not in detached scratch notes.

---name: ubsdescription: [WHAT] Static-analysis quality-gate wrapper around the external `ubs` CLI (Ultimate Bug Scanner). [HOW] Runs `ubs` on staged, diffed, or explicitly changed files with structured output, then uses the findings as a pre-commit or pre-review bug gate. [WHEN] Use before commit, during code review, when the user asks for bug scanning, or when a change needs a fast multi-language sanity pass. [WHY] Catches AI-agent bug patterns early without making UBS itself the project workflow router. Triggers: "ubs", "ultimate bug scanner", "bug scan", "static analysis", "quality gate", "scan for bugs", "pre-commit scan"---# UBSUse `ubs` as a scoped gate. Keep the scope tight unless the user explicitly wants a full baseline scan.## Prerequisites```bashcommand -v ubs```If missing, stop and tell the user:```bashbrew install dicklesworthstone/tap/ubs```## Golden Rules1. Prefer `--staged`, `--diff`, or explicit files over `ubs .`.2. Use `--format=json` when you need machine-readable output.3. Re-run after fixes to confirm the exit code is clean.4. Treat UBS as a tool boundary; do not import its repo-level hooks as implicit Lev policy.## Fast Path```bashubs --staged --format=json --ci```If you only changed a few files:```bashubs path/to/file.ts path/to/other.py --format=json --ci```## Core Commands### Narrow scans```bashubs --staged --format=json --ciubs --diff --format=json --ciubs src/file.ts src/other.py --format=json --ci```### Full or filtered scans```bashubs . --format=json --ciubs --only=js,python . --format=json --ciubs --category=resource-lifecycle . --format=json --ci```### Diagnostics```bashubs doctorubs doctor --fix```## Recommended Workflow### Before commit```bashubs --staged --fail-on-warning --format=json --ci```### During review1. Scan only the touched files.2. Inspect critical findings first.3. Fix root causes, not symptoms.4. Re-run the same narrow scan.## Output HandlingFocus on:- `summary`- `findings[].file`- `findings[].line`- `findings[].severity`- `findings[].category`- `findings[].message`If the user wants GitHub or CI artifacts:```bashubs . --format=sarif --ciubs . --report-json .ubs/latest.json --html-report .ubs/latest.html --ci```## When Not To Use UBSDo not default to UBS when:- the user wants architectural review rather than static findings- there are no changed files and no request for a baseline scan- another domain-specific checker is clearly more appropriate## Anti-Patterns- Running `ubs .` on every small edit- Ignoring critical findings without checking the code- Treating UBS findings as proof without context- Installing repo hooks or settings from the upstream repo without explicit user approval## Minimal Report Pattern```markdown## UBS Findings- Scope scanned:- Critical:- Warnings:- Follow-up fixes:```Keep the summary in the active Lev artifact or review comment, not in detached scratch notes.

Frequently asked questions

Ubs