ub-quality

Enforce uniform formatting and alignment across touched code and documentation blocks.

6|2|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/robert-hoffmann/uncle-bob --skill ub-quality
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ub-quality
Source: https://github.com/robert-hoffmann/uncle-bob/tree/main/.agents/skills/ub-quality
Command: npx skills add https://github.com/robert-hoffmann/uncle-bob --skill ub-quality

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Portable baseline quality checks to ensure consistent formatting, alignment, and documentation quality across touched code and documents.

Core Features & Use Cases

  • Enforces separator-column alignment for touched vertical blocks across code, configs, and docs
  • Loads and applies design/formatting references to guide edits and refactors
  • Use case: apply guardrails during code reviews or refactors to keep changes clean and predictable

Quick Start

Invoke ub-quality before editing touched blocks to apply mandatory alignment and documentation standards.

Frequently Asked Questions about ub-quality

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

FAQPage Schema
How do I enforce consistent code formatting and alignment during refactoring?

To enforce consistent code formatting during refactoring, apply guardrails that standardize separator-column alignment for touched vertical blocks across code, configs, and documentation files.

What is separator-column alignment for touched code blocks?

Separator-column alignment is a formatting standard that enforces uniform vertical alignment across touched code and documentation blocks, ensuring consistent style and predictable structure during edits.

Can I apply documentation structure refactoring across different file types?

Yes, documentation structure refactoring applies across languages and file types, loading references for design patterns and important tags to guide edits and maintain consistent documentation quality.

What's the best way to keep code review changes clean and predictable?

The best way to keep code review changes clean is to apply formatting and quality guardrails before editing touched blocks, ensuring uniform alignment and documentation standards are met.

Do I need specific references to guide code formatting and guardrails?

Yes, you need mandatory references like design-patterns, formatting-alignment, documentation-structure-refactoring, and important-tags-and-doc-generation files to load and apply formatting guardrails during edits.

Why does my documentation structure break when refactoring multiple file types?

Documentation structure breaks during refactoring when uniform formatting and alignment standards are not applied across touched blocks, requiring mandatory references to guide consistent style and structure.