second-opinion

Generate a self-contained markdown audit prompt for external code repository review.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/Eric-Pacheco95/claude-workbench --skill second-opinion-eric-pacheco95
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: second-opinion
Source: https://github.com/Eric-Pacheco95/claude-workbench/tree/main/.claude/skills/second-opinion
Command: npx skills add https://github.com/Eric-Pacheco95/claude-workbench --skill second-opinion-eric-pacheco95

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the creation of a detailed review prompt that an external agent can use to perform an independent audit of a code repository.

Core Features & Use Cases

  • Prompt Generation: Outputs a markdown file with a self-contained prompt ready to be pasted into an external session for independent repo audit.
  • Mode Selection: Offers read-only (static) and dynamic (full harness and runtime checks) options.
  • Parameters: Allows customization with flags for target, output path, and reviewer name.
  • Use Case: Ideal for obtaining an unbiased assessment of a codebase before a major release or regulatory review.

Quick Start

Generate a full dynamic prompt for the current working repo: /second-opinion

Frequently Asked Questions about second-opinion

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

FAQPage Schema
How do I generate an independent audit prompt for a code repository?▼

To generate an independent audit prompt for a code repository, run the command with parameters for the target repo, output file, and reviewer name to produce a markdown file containing the review instructions.

What is the difference between static and dynamic code audit modes?▼

Static code audit mode performs read-only analysis of the repository, while dynamic mode generates a prompt for full harness and runtime execution checks.

Can I customize the output path and reviewer name for my repo review prompt?▼

Yes, you can customize the repo review prompt by using input flags to specify the target repository, the desired markdown output file path, and the reviewer name.

When do I need to use an external reviewer for repository safety checks?▼

You need an external reviewer for repository safety checks when you require an unbiased independent assessment of a codebase before a major release or regulatory review.

What is the best way to prepare an unbiased assessment of a codebase?▼

The best way to prepare an unbiased assessment is to generate a self-contained markdown prompt that directs an external agent to perform an independent audit of your codebase.