santa-method

Verify AI outputs through dual independent review and fix-until-converged loops.

1|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/samymity/bridge-ventures-backend --skill santa-method-samymity
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: santa-method
Source: https://github.com/samymity/bridge-ventures-backend/tree/main/.claude/skills/santa-method
Command: npx skills add https://github.com/samymity/bridge-ventures-backend --skill santa-method-samymity

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill reduces the risk of publishing or shipping incorrect, non-compliant, or hallucinated outputs by forcing two independent reviewers to verify the same deliverable before it goes live.

Core Features & Use Cases

  • Dual independent review gate: Two separate review agents evaluate the output using the same rubric without seeing each other’s assessments.
  • Verdict convergence loop: If either reviewer flags issues, the system applies targeted fixes and re-runs both reviewers until convergence or max iterations.
  • Production-ready usage guidance: Designed for high-stakes deployment, brand/compliance constraints, and accuracy-critical content where human spot-checking is insufficient.
  • Failure mode coverage: Includes guardrails against rubber-stamping, context bleed, reviewer drift, fix regression, and infinite loops.

Quick Start

Use the santa-method skill to verify your generated customer-facing text or production code output by requiring two independent reviewers to pass the same rubric before it ships.

Frequently Asked Questions about santa-method

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

FAQPage Schema
How do I verify AI generated content for compliance and hallucinations before production release?

Verify AI generated content for compliance and hallucinations by running dual independent reviewers against an identical objective rubric, requiring both to return structured PASS verdicts before production release. Targeted fixes are applied to any flagged issues until convergence.

What is dual independent review for high-stakes AI outputs?

Dual independent review for high-stakes AI outputs is a quality gate where two isolated reviewer agents evaluate the same deliverable using the same rubric without seeing each other's assessments, preventing context bleed and rubber-stamping of non-compliant content.

How do I stop AI reviewers from rubber-stamping or drifting during compliance validation?

Stop AI reviewers from rubber-stamping or drifting during compliance validation by isolating their reviewer contexts and applying structured PASS/FAIL JSON verdicts against an identical objective rubric, ensuring independent assessments that prevent context bleed and reviewer drift.

Can I use iterative fixing for production code that fails an adversarial verification check?

You can use iterative fixing for production code that fails adversarial verification by triggering targeted re-generation of only the flagged issues, looping both reviewers until convergence or maximum iterations are reached to prevent fix regression.

When should I use a strict both-pass verdict gate for regulated language?

Use a strict both-pass verdict gate for regulated language when human spot-checking is insufficient and constraint violations are unacceptable, requiring two independent reviewers to pass the same objective rubric before deployment-ready content ships.

What are the limitations of using dual review loops for technical documentation?

Limitations of using dual review loops for technical documentation include potential infinite loops mitigated by max iterations, and the risk of fix regression requiring targeted re-generation of only flagged issues rather than full re-generation to maintain convergence.