skills.rest
srid
sridCOMMUNITY
Explore all skills by this author →
Website𝕏@sridcaGitHub

lens-debate

Automate a debate between Lowy and Hickey structural review lenses on code changes.

Updated Jun 2, 2026
Search Tags:#code review#consensus#debate#automated review#structural analysis
One-click install
npx skills add https://github.com/srid/smriti --skill lens-debate
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: lens-debate
Source: https://github.com/srid/smriti/tree/main/.claude/skills/lens-debate
Command: npx skills add https://github.com/srid/smriti --skill lens-debate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires Claude Code Workflow, and includes scripts (resource) components.

What problem does it solve?

This Skill automates a debate between two structural review lenses, Lowy and Hickey, to reach a consensus on code changes, ensuring a thorough and unbiased review process.

Core Features & Use Cases

  • Automated Debate: Lowy and Hickey lenses independently review code changes and debate until they agree on each finding.
  • Consensus-Based Commitment: Agreed fixes are applied as individual commits.
  • Use Case: When you want to ensure a code change is thoroughly reviewed before merging, use the lens-debate skill to automate the debate between Lowy and Hickey lenses.

Quick Start

Run the lens-debate skill with the PR number and specify the base branch, if needed: /lens-debate <pr-number> [--base <branch>]

Frequently Asked Questions about lens-debate

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

FAQPage Schema
How do I automate structural code review for a pull request?▼

Automated code review debates handle PR diffs by having two independent structural lenses review changes, cross-examine each other's findings, and apply consensus fixes. This resolves bias by requiring agreement before committing any suggested changes.

What is a consensus-based automated review debate?▼

A consensus-based review debate is a process where two structural lenses independently analyze code changes and cross-examine findings until they agree. Agreed fixes are then applied as individual commits to ensure thorough structural analysis.

Do I need Claude Code Workflow to run automated code review debates?▼

Yes, you need the Claude Code Workflow tool to run automated code review debates. This dependency is required to process PR diffs, manage cross-examination between lenses, and apply agreed fixes as individual commits.

How do I start a structural review debate on a specific PR?▼

To start a structural review debate, run the command with the PR number and optionally specify the base branch using the syntax /lens-debate <pr-number> [--base <branch>]. The lenses will then independently review the PR diff.

Can I use custom structural analysis lenses for code review debates?▼

Yes, you can use custom lenses for code review debates, but they require predefined frameworks. The Skill automates the debate between lenses with predefined frameworks, such as the default Lowy and Hickey structural analysis lenses.

When should I not use an automated debate for code changes?▼

You should not use an automated debate for code changes if your PR lacks a clear diff or if you do not have lenses with predefined frameworks. The consensus process depends on structural analysis lenses to generate independent reviews and reach an agreement.

Related Skills

Explore More Software Engineering Skills→
soyasissoyasis

review

Analyze diffs against the base branch to surface structural issues in PRs.

Community
Advanced
berrzebbberrzebb
15

consensus-loop:merge

Squash-merge a git worktree into the target branch with a structured commit message.

Community
Advanced
iamacoffeepotiamacoffeepot
1

review

Automate code review for Aether engine PR-bound changes.

Community
Intermediate
diiviikk5diiviikk5

review

Analyze PR diffs for SQL safety, LLM trust boundaries, and structural issues.

Community
Advanced