Skip to content
Diagnosis · Code

service-virtualization

Decision framework for isolating every external dependency in a test suite: when to use in-process mocks, HTTP stubs (MSW, WireMock), record-replay, fault…

Examining code for the line that is wrong

Works with
ClaudeChatGPTGeminiClaude CodeCodexCursorCopilotGemini CLI
Setup
Upload one file
About a minute in Claude. One command in coding tools.
Contains
Instructions only
Text files — no scripts or programs.
Maintained
Last change 10 Jun 2026
On the repository’s main branch.

What it does

<objective> Mock Stripe at the SDK layer and your tests pass green while production 500s the moment Stripe changes a response field — because the stub was never tied to a contract.

Read more

This skill picks the right isolation strategy per dependency (in-process mock, HTTP stub, record-replay, fault injection, or ephemeral real service), stubs at the HTTP layer so tests survive SDK upgrades, and makes the CI run fail when any real call escapes the stubs. </objective>

What it can touch

  • No script files in its folder

    Its folder holds text, not programs — but the instructions do tell your AI to run commands (see below).

    How we know

    Listed the 7 files in the skill’s folder on GitHub; none is a script or program.

  • Uses terminal commands

    It shows your AI commands to run. In a coding agent that means your terminal; in a chat app it usually can’t.

    How we know

    The SKILL.md contains shell code blocks.

  • No known risk pattern found

    Launch7’s automated check read all 7 text files in this skill and matched none of its risk patterns. This is not a guarantee: a check like this can miss new or disguised tricks, and the author can change the files after the check.

    How we know

    Read 2026-10-05, commit b3bb61b by pipeline/trust/analyze.py — 40+ patterns for hidden text, prompt injection, downloads that run, credential access and more. It reads; it never runs the skill.

  • Updated this year

    Its repository has had changes recently.

    How we know

    Last push to petrkindlmann/qa-skills: 2026-06-10 (117 days before the scan).

Read automatically from the skill’s own files on GitHub on 5 Oct 2026. Launch7 does not run or manually review skills: this lists what the check saw, and nothing here means “safe”. How we check

Add it to your AI

Supported. Upload it once in Claude’s settings. Works on every plan, including Free.

  1. Built in your browser from the SKILL.md on GitHub — nothing passes through Launch7.

  2. In Claude, open Customize → Skills, press +, then Create skill → Upload a skill, and choose the .zip.

  3. Make sure code execution is switched on (Settings → Capabilities). Skills need it.

  4. Start a new chat and ask for the job in your own words — Claude picks the skill up when it fits.

How Claude does this: support.claude.com · checked 28 Sep 2026 · “Supported” means documented by the vendor; Launch7 has not run it end to end

More from petrkindlmann

All from this publisher →
  • ai-qa-review

    Review EXISTING test code for quality, smells, and testability issues.

    petrkindlmannInstructions only
  • compliance-testing

    Test for regulatory compliance: GDPR/CMP consent verification, Google Consent Mode v2, Global Privacy Control (GPC), CCPA/US state opt-out, EU AI Act…

    petrkindlmannRuns terminal commands
  • cross-browser-testing

    Design analytics-driven browser test matrices and execute cross-browser tests.

    petrkindlmannInstructions only
  • database-testing

    Validate database integrity, test migrations forward and backward, verify schema constraints, manage seed data, detect migration drift, and identify query…

    petrkindlmannInstructions only
  • payment-testing

    Test payment and checkout flows end to end against PSP sandboxes — Stripe first, with the general pattern for Adyen/Braintree/PayPal.

    petrkindlmannRuns terminal commands