Agent skill · Testing & QA

mocking-stubbing

Use this skill at Step 9 of the v2 SOP to run the change's tests against the stage-isolated synthetic mock data produced at Step 5. Handles fixture loading, mock service stand-up (DB / external APIs / LLM endpoints), runs the test pyramid (unit + integration + e2e where applicable), and produces a test result report. On failure, hand off to systematic-debugging. Chinese trigger examples: "mock 测试", "Step 9", "跑测试用 mock", "联调 mock", "存根服务测试". Do NOT use to test against production data, do NOT use without verified mock fingerprints. Success = all tests green against stage mock, test result XML

Bill Blasco95★ · 1 repos on radarProfile →
claude-codeApache-2.0
Install
npx skills add charliehzm/medharness --skill mocking-stubbing --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 2 KB
Bundled scripts: none
Version: 1.0
Requires: Requires test runner; mock service stand-up (docker-compose or in-process). LLM mock returns deterministic stub…
Path: .claude/skills/mocking-stubbing/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 96 · +1 this week
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Mocking Stubbing The "tests must pass against synthetic data" gate. ## Mock layers | Layer | What's mocked | How | |---|---|---| | DB | All persistence | sqlite-in-memory or testcontainers + synthetic fixtures | | External APIs | Hospital HIS / 3rd party | responses library / wiremock | | LLM | Model calls | deterministic stub via mcp-model-router test mode | | Time | clocks | freezegun / fake c

More from medharness
All skills →
About this skill
What does the mocking-stubbing skill do?

Use this skill at Step 9 of the v2 SOP to run the change's tests against the stage-isolated synthetic mock data produced at Step 5. Handles fixture loading, mock service stand-up (DB / external APIs / LLM endpoints), runs the test pyramid (unit + integration + e2e where applicable), and produces a test result report. On failure, hand off to systematic-debugging. Chinese trigger examples: "mock 测试", "Step 9", "跑测试用 mock", "联调 mock", "存根服务测试". Do NOT use to test against production data, do NOT use without verified mock fingerprints. Success = all tests green against stage mock, test result XML

How do I install it?

Run `npx skills add charliehzm/medharness --skill mocking-stubbing --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From charliehzm/medharness, a repository with 96 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going