Menu
AI-driven test execution. Opus decides what to run and how confident to be, based on your diff.
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/antiwork/gumroad --skill test-confidenceThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Execute read-only Ruby/Rails commands against Gumroad's production database for debugging and investigation. Use when the user needs to debug production issues, look up data, investigate user reports, check records, or query production state. Triggers on: "check in prod", "debug this in prod", "look up user/purchase/product in production", "production console", "investigate in prod", "query production", "what's happening in prod", "look up a user by email", "who bought this product", "why is this user blocked", "find this sale/purchase", "how many X does Y have", or any request to examine live Gumroad data — even when the user doesn't say "prod" explicitly.
Review GitHub pull requests for the Gumroad codebase against project guidelines, code quality, and correctness. Use when the user wants to review a PR, check new comments on a PR, provide feedback on code changes, or asks about PR quality. Triggers on: "review PR", "review this PR", "check PR #NNN", any GitHub PR URL (e.g. https://github.com/antiwork/gumroad/pull/NNNN), "what's new on the PR", "check comments", "review the diff", "give feedback on this PR", or requests to evaluate code changes in a pull request.
Stage and commit changes with a clear, concise commit message.
Based on SOC occupation classification
Showing SKILL.md
| name | test-confidence |
| description | AI-driven test execution. Opus decides what to run and how confident to be, based on your diff. |
| argument-hint | --full to run to 100% | --strict to halt on pre-existing failures |
| allowed-tools | Bash(git *), Bash(bundle exec rspec *), Bash(cat *), Bash(find *), Bash(wc *), Bash(head *), Bash(tail *), Bash(grep *), Bash(bin/test-confidence *) |
Run bin/test-confidence to have Opus 4.7 analyze your diff, decide the risk level, plan which tests to run and in what order, and set confidence milestones. The AI decides the shape of the curve based on this specific diff.
bin/test-confidence # Run to 99%, stop. Skips past pre-existing failures.
bin/test-confidence --full # Run to 100%
bin/test-confidence --strict # Halt on any failure, including pre-existing
ANTHROPIC_API_KEY is auto-sourced from .env if not exported.
If $ARGUMENTS is provided, pass it through: bin/test-confidence $ARGUMENTS
tmp/test-confidence/ for a cached plan; reuses if found--full, continues running remaining tests toward 100%When a spec fails, the script applies a two-step check:
app/models/user.rb for spec/models/user_spec.rb) appear in the diff?
main.
The verify step is skipped (heuristic verdict trusted) when the diff includes a db/migrate/*.rb (DB schema drift) or Gemfile.lock (bundler drift), or when no merge-base is available. --strict skips both checks and halts on every failure.
Cost profile: zero overhead in the common no-failure case; verify only runs on heuristic-flagged "pre-existing" failures. Catches the dangerous direction (silent regression skipped) while keeping false-alarm investigation costs bounded.
The key insight: Opus decides ad hoc how many tests are needed for each confidence level. A comment-only change might need 2 tests for 99%. A payment model refactor might need 100.
Run this before every commit. It replaces manually picking which specs to run.
$ARGUMENTS