ubs

Run UBS on changed files to surface code review findings.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Dunc4nJ/agent-skills --skill ubs-dunc4nj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ubs
Source: https://github.com/Dunc4nJ/agent-skills/tree/main/skills/ubs
Command: npx skills add https://github.com/Dunc4nJ/agent-skills --skill ubs-dunc4nj

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

UBS helps developers catch issues that slip through normal testing by scanning changed code and surfacing actionable findings during code review.

Core Features & Use Cases

  • Run UBS on staged changes, diffs, or entire project to quickly surface potential defects.
  • Triage findings to differentiate real bugs from false positives and guide remediation.
  • Suppress false positives with justification documented in code annotations.

Quick Start

Run UBS on your staged changes to start a fast pre-commit review.

Frequently Asked Questions about ubs

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

FAQPage Schema
How do I automate static analysis for pre-commit code review?

Automating static analysis for pre-commit code review involves scanning staged changes to surface potential defects and triage findings before code is committed. This enforces robust frontmatter and provides clear remediation guidance.

What is the best way to triage static analysis findings during a pull request review?

Triage static analysis findings during a pull request by differentiating real bugs from false positives and guiding remediation. UBS automates this workflow by scanning changed files and surfacing actionable triage insights directly in the review process.

Can I run static analysis on unstaged changes or the entire project?

Yes, you can run static analysis on unstaged changes or the entire project. The tool supports scanning staged changes, unstaged diffs, and full project updates to surface potential defects across different code review and CI scenarios.

How do I suppress false positives in static analysis with documented justification?

You suppress false positives in static analysis by adding documented justifications directly in code annotations. This ensures that suppression decisions are explicitly recorded within the codebase for future reference and review.

Does UBS require any external dependencies to scan staged changes?

No, UBS does not require external dependencies to scan staged changes. It operates independently to automate code review workflows by running static analysis on changed files and surfacing actionable findings.