dcr

Automates recursive multi-lens code review to validate changes until all selected checks pass.

1|Updated Jan 19, 2026
One-click install
npx skills add https://github.com/jackneil/claude-jacked --skill dcr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dcr
Source: https://github.com/jackneil/claude-jacked/tree/main/jacked/data/skills/dcr
Command: npx skills add https://github.com/jackneil/claude-jacked --skill dcr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures code changes receive a comprehensive, multi-lens review to improve reliability and safety after non-trivial code changes.

Core Features & Use Cases

  • Recursive, multi-lens evaluation continues until all selected checks pass.
  • Applies to feature implementations, bug fixes, and refactors to catch edge cases early.
  • Integrates with common development workflows to enforce code quality before merging.

Quick Start

Run the dcr workflow on your latest change to trigger recursive lens reviews until all selected lenses pass.

Frequently Asked Questions about dcr

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

FAQPage Schema
How do I automate multi-lens code review for a pull request?

You can automate code review by running a recursive workflow that validates changes across multiple configurable lenses. It continues evaluating until all selected checks pass, applying to features, bug fixes, and refactors.

What is recursive code review and how does it improve software quality?

Recursive code review repeatedly applies multiple evaluation lenses to code changes until all checks pass. It ensures quality by catching edge cases early across features, bug fixes, and refactors before merging.

Can I configure specific quality assurance lenses for my code review?

Yes, the code review process supports configurable lens sets. You select specific quality assurance lenses to evaluate changes deterministically, with execution halting automatically when any chosen lens fails.

Does automated recursive code review work for complex refactors?

Yes, automated recursive code review works for complex refactors across software projects of varying sizes. It validates non-trivial changes across multiple lenses to ensure reliability and safety before merging.

What happens when a code review lens fails during the automated check?

When a code review lens fails, the automated process halts immediately. This deterministic behavior ensures changes are not approved until all failing lens checks are resolved and the recursive review passes.

When do I need to use an automated multi-lens code review workflow?

You need a multi-lens code review workflow after non-trivial code changes to ensure reliability and safety. It validates feature implementations, bug fixes, and refactors to catch edge cases before merging.