agentleFS
storybookjsstorybookjs/storybook/.agents/skills/second-opinion/SKILL.md

second-opinion

Skill92k starsChanged 5 days agoMITView on GitHub

Gets a blind review of a diff or a PR from a model of another provider (Claude, GPT, Gemini), then checks and compares its findings. Use when the user asks for a second opinion, an adversarial review, or a review by another model.

48 other projects use a version of this.

Trending

More talk lately.about the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 2 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 1 mentionOct 2026: 2 mentionsNov 2026: 1 mention
Dec 2025Jun 2026Nov 2026
Mentions a month of the storybookjs/storybook repository that our weekly crawl found. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about storybookjs/storybook

The biggest 5 of 89 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 89

Talked about on Stack Overflow, YouTube, GitHub, Bluesky and Hacker News (89 times).

On Stack Overflow · 30

25 more on Stack Overflow

On YouTube · 25

20 more on YouTube

On GitHub · 19

14 more on GitHub

On Bluesky · 13

8 more on Bluesky

Used with

Projects with it also use insecure-defaults, variant-analysis and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • allanninalSkill

    insecure-defaults

    Detects fail-open insecure defaults (hardcoded secrets, weak auth, permissive security) that allow apps to run insecurely in production. Use when auditing security, reviewing config management, or analyzing environment variable handling.

    Also in 3 projects that use this

  • allanninalSkill

    variant-analysis

    Find similar vulnerabilities and bugs across codebases using pattern-based analysis. Use when hunting bug variants, building CodeQL/Semgrep queries, analyzing security vulnerabilities, or performing systematic code audits after finding an initial issue.

    Also in 3 projects that use this

  • shmehroSkill

    ux-audit

    Perform a heuristic UX audit on a UI screen, flow, or component description

    Also in 3 projects that use this

  • sunnyclinches44Skill

    explain

    Explains code using real-world analogies and ASCII diagrams

    Also in 5 projects that use this

  • photon-groveSkill

    unslop

    Detects and rewrites generic, overly polished, or AI-sounding prose while preserving meaning. Use when the user asks to "unslop", humanize, de-AI, tighten, or review whether writing sounds generated.

    Also in 4 projects that use this

  • SentrySkill

    deslop

    Strip AI-generated noise from the diff before pushing — extra comments a human wouldn't write, defensive try/catch in trusted code paths, casts to any, inline imports in Python, and other style inconsistencies with the surrounding file. Use this immediately before commit so the diff stays clean.

    Also in 3 projects that use this

The file

Files
SKILL.md

Second opinion

A second opinion is a blind review: a model from another provider, in a fresh session, judges the change without seeing your view. Its value is independence, and another provider has other blind spots than yours. So the brief carries the goal and the change, and keeps your conclusions back.

Steps

  1. Pin the change. The base ref and head (git diff <base>...HEAD), or the PR number. Done when you can name it by ref or URL.
  2. Pick the reviewer. A model of another provider than yours, at its default effort. When no other provider is available, use a stronger model of your provider (for example Fable instead of Opus), or your own model at a higher reasoning effort. The user's choice wins.
  3. Write your own view first. A few lines: the risks you see and your verdict. Keep it out of the brief. It is your baseline for step 6.
  4. Write the brief to a temporary file:
    • Context: what the change is for, in two or three sentences, and the spec (the issue, or the PR body).
    • Change: the refs and the diff command, or the PR URL.
    • Known and accepted: findings already judged and left on purpose, so the reviewer skips them.
    • Rule: the section "Edge cases and guards" from the code-review rules, pasted in full.
    • Scope, verbatim: "You may read files and run read-only commands. Change nothing, and post nothing to GitHub: this is a review."
    • Output, verbatim: "Reply with a one-line verdict, then numbered findings, most severe first. For each: severity (blocker, major, minor, nit), file:line, the problem, a concrete failure scenario (inputs, then the wrong result), the producer of its input, and your confidence. End with the files and commands you checked."
  5. Run the reviewer from the checkout, read-only, in the background. Use the first that your environment has:

    • A delegation tool of your agent environment that can start a session on another provider (for example T3 Code's delegate_task).
    • The other provider's CLI: codex exec -s read-only -m <model> -o <reply-file> - < <brief-file>, or claude -p --permission-mode plan --model <model> < <brief-file> > <reply-file>.
    • A subagent on the model from step 2, when no other provider is available. Give it the brief only, not this conversation.

    Tell the user which model reviews. A reviewer of your own provider shares more of your blind spots, so say so in the report.

  6. Check and compare. The reviewer can be wrong. Check each finding against the code yourself, and give it a verdict: confirmed, or disputed (with the reason). For a finding that names no producer of its input, judge it as "Edge cases and guards" says. Then report: both verdicts, new confirmed findings your baseline missed, shared findings, disagreements, and what neither of you checked.

Done when every finding has a verdict with a reason.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.