ultramode-code-review

Review code changes against project invariants using multiple reviewer lenses.

Updated Feb 22, 2026
One-click install
npx skills add https://github.com/mbriggsy/ai-learning-journey --skill ultramode-code-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ultramode-code-review
Source: https://github.com/mbriggsy/ai-learning-journey/tree/main/projects/skills/ultramode-code-review
Command: npx skills add https://github.com/mbriggsy/ai-learning-journey --skill ultramode-code-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Holistic, contract-calibrated code reviews ensure software changes adhere to project invariants.

Core Features & Use Cases

  • Whole-file assessment: reads entire modules to catch cross-file interactions and invariant violations, not just diffs.
  • Multi-lens review: applies correctness, architecture, testing, simplicity, and API-contract lenses with adversarial verification.
  • Proactive governance: uses a contract brief, formal review workflow, and distal distillation of insights for future work.

Quick Start

Run ultramode-code-review on the target unit to generate a comprehensive, contract-calibrated review before merge.

Frequently Asked Questions about ultramode-code-review

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

FAQPage Schema
How do I perform a holistic code review that checks for cross-file invariant violations?

Holistic code review reads entire modules to catch cross-file interactions and invariant violations, not just diffs. It applies multiple reviewer lenses with adversarial verification to validate findings against the source before merging.

What is a contract-driven code review and how does it enforce project invariants?

Contract-driven code review enforces a contract brief to ensure software changes adhere to project invariants. It applies formal review workflows at unit or milestone boundaries and distills lessons into repeatable improvements.

How do I apply multiple review lenses to validate code correctness and architecture?

Apply correctness, architecture, testing, simplicity, and API-contract lenses to evaluate code changes. Adversarial verification validates findings against the source before merging, ensuring comprehensive multi-lens coverage.

Can I use whole-file assessment for code reviews instead of just reviewing diffs?

Whole-file assessment reads entire modules to catch cross-file interactions and invariant violations that diff-based reviews miss. It operates at unit or milestone boundaries to generate comprehensive, contract-calibrated findings before merge.

What's the best way to automate adversarial verification of code review findings?

Adversarial verification validates review findings against the source by orchestrating multiple reviewer lenses. It enforces a contract brief and presents structured findings, distilling lessons into repeatable improvements for future work.