double-check

Verify finished work through adversarial multi-round review by a different AI provider's CLI agent.

3|Updated Nov 8, 2014
One-click install
npx skills add https://github.com/mintuz/.dotfiles --skill double-check-mintuz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: double-check
Source: https://github.com/mintuz/.dotfiles/tree/main/agents/.agents/skills/double-check
Command: npx skills add https://github.com/mintuz/.dotfiles --skill double-check-mintuz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? A model reviewing its own work shares every blind spot that produced the bugs, so self-review mostly re-confirms existing assumptions. This Skill gets a genuinely independent second opinion from a different AI provider's CLI agent and runs a structured back-and-forth until both agents converge. ## Core Features & Use Cases - Cross-provider verification: Detects the host agent and selects a verifier from a different model lab (codex, claude, gemini, or cursor-agent), with a clearly labelled same-provider fresh-context fallback when no independent provider is available. - Adversarial review loop: Sends a structured brief, collects severity-tagged findings, fixes or rebuts each one, and re-verifies across rounds using a findings ledger until explicit convergence. - Rigor and safety controls: Uses the best available model with maximum reasoning effort, read-only sandboxing, stdin-based briefs, and guardrails against leaking secrets to external providers. - Use Case: Before merging a security-sensitive PR, ask for a double-check; a Codex verifier at xhigh effort attacks the diff, you fix two findings and rebut one, and after three rounds both agents agree it is safe to merge. ## Quick Start Ask the agent to double check the finished work with a second opinion from another AI provider before merging.

Frequently Asked Questions about double-check

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

FAQPage Schema
How do I get a second opinion on my code from another AI model?

Ask the agent to double-check the work; it detects the host provider, picks a CLI from a different model lab such as codex or gemini, sends a structured adversarial brief, and iterates on findings until both agents agree.

How does cross-provider AI code review work?

The host writes a brief describing the task, claim, work location, and context, then pipes it on stdin to a verifier CLI running with maximum reasoning effort in a read-only sandbox. Findings are fixed or rebutted and re-verified over multiple rounds until convergence.

What AI CLI providers can act as verifiers?

Supported verifiers are codex (OpenAI), claude (Anthropic), gemini (Google), and cursor-agent with a model from a different lab. The verifier's underlying model lab must differ from the host's for the review to count as independent.

What happens if no other AI provider CLI is installed?

The skill falls back to launching a fresh same-provider agent with zero inherited context, clearly labelled as a same-provider fresh-context fallback. This reduces anchoring but lacks model-lab diversity, and the reduced independence is reported explicitly.

When should I not use a double-check review?

Skip it for trivial changes like typos or formatting, for unfinished work, and when no separate reviewer context can be launched. Verifier calls cost significant tokens and time, so reserve them for high-stakes or complex work.

Is it safe to point an external AI verifier at my repository?

The verifier runs read-only by default, but any file it is pointed at may be transmitted to another provider. Redact or exclude secrets, credentials, and customer data from scope before invoking an external verifier.