Test standard as an installable plugin — the execution-tier split, the test contract, the axes a case space is derived from, factories, matchers and fakes, a JSON failure envelope, and the coverage and mutation gates. Ships a whole-tree audit agent and the config a repository states its own numbers in.
Plugin tests from marketplace bladeforge in aquivalabs/BladeForge. Commands read from the repo's manifest — 2 days ago.
apexUse when writing, fixing, or extending an Apex test — a test class for a new or changed Apex class, a negative or bulk path, a `@TestSetup` factory, swapping `System.assertEquals` for `Assert.*`, removing a hardcoded record Id, mocking a `RestRequest` for a `@RestResource`, covering a `WITH USER_MOD
architectureUse when writing, reviewing, moving, or speeding up a unit test — deciding which execution tier a test file belongs to, what a test must satisfy to be accepted, or how coverage and mutation-score gates apply. Also when a test is slow, flaky, or green while the code under it is wrong.
test-auditorRead-only, whole-repo audit of a test suite against the test standard's own numbered rules — including the ones nothing runs unattended.
Stack-agnostic pre-push review framework — eight reviewer agents (five on by default, plus skill, leak and security-scan for repos that publish skills), the /review orchestrator, and the secret-scan + attestation gate, all driven by a per-project .claude/review.config.json.
2 skills · 2 commands · 8 agents
Meta skills — authoring new skills, the OCKHAM minimal-entities discipline, and the WITTGENSTEIN clarity gate for specs & plans.
10 skills
Frontend Vue 3 skills — single-file components with Composition API and TypeScript, component architecture, BEM in scoped styles, Pinia stores, VueUse-first composables, Nuxt conventions, motion, testing.
9 skills
Frontend React skills — component structure, hooks registry, skeleton components, Storybook stories.
8 skills
Personal Salesforce skills — Apex test authoring standard and salesforce-dx MCP usage.
5 skills
Whose Turn, the Claude Code side of a local monitor of your Jira, GitHub, Linear and other sources: whose turn it is, what changed, your own to-dos, a summary at the start of each session, a hand-off from the monitor window into the session, a /whose-turn command that opens the window, and an MCP server for any agent. The monitor itself is the published whose-turn npm package; the plugin installs its latest version into the monitor's data directory on first start and runs it from there; each newer version is then announced in its window and at session start and installs only when the user says yes or clicks Update. Employer-specific values live in a workspace config on the machine, not in the plugin.
1 skill · 1 command · 1 MCP server · hooks
Matt Pocock's agent skills for real engineering (grilling, spec/ticket flows, TDD, code review, domain modelling and more).
39 skills
Automates browser interactions for web testing, form filling, screenshots, and data extraction
12 skills
Backend API design, GraphQL architecture, workflow orchestration with Temporal, and test-driven backend development
9 skills · 1 command · 8 agents
Long-term semantic memory for Claude Code, powered by OpenViking
5 skills · 1 command · 1 MCP server · hooks
Connect providers and targets, write eval suites, and set up or run red team scans with promptfoo
4 skills
Automates browser interactions for web testing, form filling, screenshots, and data extraction
1 skill
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.