second-opinion

Sends named code files to the OpenAI API for an independent adversarial review.

Updated Jun 9, 2026
One-click install
npx skills add https://github.com/timikalo7/Execute --skill second-opinion-timikalo7
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: second-opinion
Source: https://github.com/timikalo7/Execute/tree/main/.claude/skills/second-opinion
Command: npx skills add https://github.com/timikalo7/Execute --skill second-opinion-timikalo7

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When the same model family writes the code and runs every review gate, both sides share the same blind spots. This Skill gets a genuinely independent code review from a non-Anthropic model (OpenAI API) after all internal gates pass, catching issues a same-family evaluator structurally cannot see. ## Core Features & Use Cases - Cross-model code review: Sends only the files you name on the command line to the OpenAI chat completions API with an adversarial review prompt demanding file, line, breakage, and failing input per finding. - Targeted questions: The --ask flag lets you pose a specific concern (e.g., a suspected edge case in call-site resolution) alongside the general review. - Explicit failure diagnosis: Detects quota and billing errors and states plainly that a ChatGPT/Codex subscription does not include API credit, so the failure is not mistaken for a bug. - Use Case: After a build passes every internal quality gate, run the script on the core module with a pointed question to get a dissenting review before shipping, then verify each finding against the code before acting on it. ## Quick Start Set OPENAI_API_KEY in the environment and run node review.mjs with the files to review, optionally adding --ask with a specific question.

Frequently Asked Questions about second-opinion

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

FAQPage Schema
How do I get a second opinion on AI-generated code from a different model?

Run the review.mjs script with the files to review as arguments and OPENAI_API_KEY set in the environment. It sends only those files to the OpenAI API with an adversarial prompt and prints findings with file, line, and failing input.

How do I ask a specific question during an automated code review?

Pass the --ask flag followed by your question, for example asking whether call-site resolution has a silently wrong case. The question is appended to the review prompt so the model addresses it directly alongside general findings.

Why does the OpenAI API call fail even with an active ChatGPT subscription?

A ChatGPT or Codex subscription does not include API credit; they are separate billing meters. Add a balance at platform.openai.com under Billing, and the script explicitly names this quota failure when it occurs.

Is it safe to send code files to a third-party model for review?

Only the files named on the command line are sent, and the API key is read from the environment and never written anywhere. Read files before sending and never include personal data without the owner's explicit decision.

Should I trust the findings from a different model's code review?

Treat the output as one more opinion, not a verdict. A different model is confidently wrong in different places, so verify every finding against the actual code before acting on it.