Teaches Claude to write, review, and audit tests worth having — behavior-focused design, disciplined test doubles, browser and component testing, a plan-gated pipeline that turns a ticket or PR into tests of the described behavior, a check on whether pushed code still matches the description that specified it, and a repo-scale map of where test protection is weakest
Plugin testing from marketplace bobtat-plugins in bobtat/claude-plugins. Commands read from the repo's manifest — today.
behavior-extractionUse when turning a described behavior — a JIRA ticket, a GitHub PR or issue, a spec document, or free-form text — into a structured, testable behavior specification before any test is planned or written. Produces numbered behaviors in Given/When/Then anchored to quotes from the source, plus an expli
spec-conformanceUse when checking whether code that was written or pushed actually does what its description said — comparing a PR, branch, or commit range against the ticket, issue, or acceptance criteria that specified it, and returning a per-behavior verdict with code citations rather than a test suite. Answers
spec-test-verificationUse when auditing written tests back against the behavior specification and test plan that produced them — checking traceability in both directions, running the full suite, classifying every failure as a spec/code mismatch versus a test defect versus an environment problem, and reporting which descr
spec-test-writingUse when implementing an approved test plan — building shared test scaffolding before fanning out, dispatching parallel authoring agents over disjoint files, requiring executed-and-observed-red evidence rather than claims of verification, and running an adversarial review of the resulting test code
test-auditingUse when assessing a whole repository's test suite rather than specific test files — finding where protection is weakest, diagnosing systemic problems across the suite, ranking modules by risk against the strength of their tests, and producing a map that says where to spend test effort next. Invoked
test-planningUse when turning a behavior specification and codebase recon into an approved test plan — choosing test cases and coverage depth per behavior, picking the right scope (unit, integration, contract, schema, property, UI, E2E), justifying every choice, running an adversarial critique of the plan, and r
testingThis skill should be used whenever writing, reviewing, or fixing tests — when the user asks to "write tests", "add tests for X", "test this function/class", "improve test coverage", "review my tests", "why is this test flaky", "should I mock this", "how do I test X", mentions TDD or characterization
/testing:spec-conformanceCheck whether pushed code still does what its ticket or PR description said — per-behavior verdicts with code citations, corroborated by the tests that already exist
/testing:test-auditAudit a whole repository's test suite — where protection is weakest relative to risk, what's systemically wrong, and where to spend test effort next
/testing:test-reviewAudit tests for quality — behavior vs implementation coupling, mock overuse, missing cases, flakiness, and tests that cannot fail
/testing:test-writeWrite tests from a described behavior — a ticket, a PR, or free text — verifying the code captures what was described, not that it does what it already does
spec-test-authorWrites test code for an assigned slice of an approved test plan, taking expected values only from the behavior specification, running what it writes, and reporting failures as findings rather than adjusting assertions to reach green. Spawned in parallel by /test-write, one per disjoint set of test f
suite-auditorAssesses the test protection of one area of a codebase and reports an aggregate verdict — how strong the protection is, what class of defect would slip through, and which patterns recur within the area. Spawned in parallel by /test-audit, one per ranked area. Read-only; reports rather than enumerati
test-code-criticAdversarially reviews newly written test code against the behavior specification and plan that produced it — checking that expected values trace to the spec rather than the implementation, that each test proves the behavior it claims, and that the code is simple, maintainable by humans, and conforma
test-plan-criticAdversarially reviews a spec-driven test plan against the behavior specification that produced it — hunting oracle contamination, fabricated requirements, missing behaviors and boundaries, wrong scope, and redundancy. Spawned by /test-write after a plan is drafted. Reports findings only; never edits
test-plannerDesigns a test plan from a behavior specification and codebase recon — choosing cases, coverage depth, and scope per described behavior, with a traceability matrix and written justification for every choice including the omissions. Spawned by /test-write; expects absolute paths to behavior-spec.md a
Interactive, human-in-the-loop QA walkthroughs of finished functionality — drives a browser, an API, and a CLI against a ticket's acceptance criteria and its merged PR, with an adversarial critic pass on both the behavior spec and the step plan, drafter/critic revision rounds, and a report with embedded screenshots. Not automated test-code authoring; that's what the testing plugin is for
5 skills · 1 command · 7 agents · 1 MCP server · hooks
Teaches Claude to build the evidence record a performance review needs before the evidence is gone — a session hook that distils each transcript into a redacted digest of your own prompts before Claude Code's 30-day purge deletes it, keeping the decisions and discarding the tool output where the secrets live; a sweep that reconciles git, PR, and review history against the journal and interviews the gaps; and authoring that turns dated entries into a review, a promotion case, or resume bullets without inventing a number
4 skills · 5 commands · 1 agent · hooks
Teaches Claude to model and check jewelry in Blender with the JewelCraft add-on over a Blender MCP connection — prong grip, seat clearance and stone overlaps measured rather than eyeballed, ring sizes read from the band's actual inner surface, metal weight with overlapping parts counted once, print/cast checks that confirm an STL comes out in millimetres, and metalwork built from editable paths fused with Geometry Nodes, split into a cast part and a hand-built wire head with a 1:1 bending template, with the add-on's scripting traps documented and worked around
11 skills
Teaches Claude to treat version control as a deliverable — atomic conventional commits split from a working tree, branch history made legible without interactive rebase, and pull requests that describe the change rather than the diff, with hooks that route version-control requests to it and block the irreversible mistakes
3 skills · 3 commands · 1 agent · hooks
Teaches Claude to edit its own prose — the catalog of tells that mark machine-written text, the clarity moves that rebuild a sentence around its real subject and verb, and the never-invent rules that keep an edit from becoming a rewrite, with a command that runs an edit pass over a draft and an agent that reads a finished document cold
2 skills · 2 commands · 1 agent
Adversarial review of a PR, plan or document by an isolated reviewer that never sees the author's context, with a triage pane deciding which findings reach the author
1 MCP server
Matt Pocock's agent skills for real engineering (grilling, spec/ticket flows, TDD, code review, domain modelling and more).
39 skills
Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques
15 skills · hooks
Harness-native ECC operator layer - 71 agents, 314 skills, 98 legacy command shims, reusable hooks, rules, selective install profiles, and production-ready workflows for Claude Code, Codex, OpenCode, Cursor, and related agent harnesses
200 skills · 98 commands · 71 agents · 1 MCP server · hooks
Collection of example skills demonstrating various capabilities including skill creation, MCP building, visual design, algorithmic art, internal communications, web testing, artifact building, Slack GIFs, and theme styling
19 skills
Comprehensive PR review agents specializing in comments, tests, error handling, type design, code quality, and code simplification
1 command · 6 agents
Production-grade engineering skills covering every phase of software development: spec, plan, build, verify, review, and ship.
25 skills · 4 agents
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.