GitPad
Back to board

unclebob/ub-mode

unclebob · personal account · GitHub id 36901
GitHub

No description on GitHub.

tools
Verify the dev 18k followerson GitHub since 2008106 public repos Gurnee, IL

Straight from the GitHub profile. The social links are the ones GitHub shows on github.com/unclebob: nothing here is submitted to GitPad.

Stars
3.2k
Velocity
1125.1★/day
Forks
158
Language
–
Created
2026-10-25 (4d)
Last push
2026-10-25
Category
tools
GitPad score
88/100
Fee lock

When this repo launches on GitPad, 100% of creator fees are locked on-chain to unclebob's GitHub vault. The split can never be changed after launch, by anyone. unclebob claims by connecting GitHub on pump.fun.

7gKjGLjmd4xqYBZRYJ7oWNzuBhvt7CAWQstZH5uYHTmH
vault live

In short

ub-mode is an agent skill, distributed as a single SKILL.md file, that directs an AI coding agent to follow a set of software engineering practices when writing or changing code. The practices are organized into three phases: first getting code working through test-driven development and domain-focused architecture, then correcting root causes and refactoring against quality thresholds, and finally maintaining logs, commits, and context discipline. It is paired with companion tools from the same author that measure cyclomatic complexity and CRAP scores, detect structural duplication, and run mutation testing to check test thoroughness.

Written by GitPad research from the repo’s public material. The full text follows below.

README · straight from GitHub

ub-mode

ub-mode is an agent skill that enforces disciplined software engineering principles when writing or changing code. It is loosely based on portions of @poteto's rules (poteto-mode / pstack), reduced and paired with deterministic quality-gate tools:

  1. First Make it Work — Laziness Protocol, Foundational Thinking, TDD, Redesign From First Principles, Attack the Premise, Subtract Before You Add, Outcome-Oriented Execution, Build the Lever, and Architecture (Model the Domain, Boundary Discipline, Type System Discipline, Make Operations Idempotent, Separate Before Serializing Shared State).
  2. Then Make it Right — Fix Root Causes, Sequence Work into Verifiable Units, Test Behavior (Not Implementation), Crapper (CRAP < 10), Dryer (duplication < 0.8), Mutator (cover the uncovered, kill the survivors, delete dead code), and Refactoring.
  3. Practice — Keep a Log, Guard the Context Window, Worktree Cleanup, and Commit and Push in small ordered commits.

Companion Tool Repositories

ub-mode relies on deterministic quality-gate tools to enforce structure, complexity, duplication, and test thoroughness:

  • unclebob/crapper — Computes cyclomatic complexity, test coverage, and CRAP score per function so every function stays under the CRAP threshold (< 10).
  • unclebob/dryer — Detects structural code duplication so duplicate blocks (>= 0.8 similarity) are eliminated.
  • unclebob/mutator — Runs mutation testing to expose uncovered code and surviving mutants that tests fail to catch.
  • unclebob/uml-viewer — Visualizes components, coverage, CRAP, mutation scores, and dependency directions.

Installation

Copy SKILL.md into your agent's skills directory as ub-mode/SKILL.md (for example ~/.grok/skills/ub-mode/SKILL.md, ~/.claude/skills/ub-mode/SKILL.md, or ~/.cursor/skills/ub-mode/SKILL.md), then invoke /ub-mode.