mattpocock-skills
claudeMatt Pocock's agent skills for real engineering (grilling, spec/ticket flows, TDD, code review, domain modelling and more).
39 skills
Answers structural questions about a repository from a resolved graph of what refers to what, and surfaces what it already knows at the moment you are about to change something. Install it and work normally — there is nothing to run.
Plugin vesta from marketplace causum in kanjani-ai-research/Vesta. Commands read from the repo's manifest — 20 days ago.
This plugin runs code on your machine — its hooks fire automatically on events like tool use and it starts local MCP servers. The exact commands are listed below; read them before installing.
vestaUnderstand an unfamiliar repository, find what is worth fixing in it, recall what its user has already decided, and record a rule the moment they state one. Use when asked what a codebase does, where some kind of work happens in it, what a change would affect, what to clean up or improve, why someth
/vesta:bearsWhether a rule you set is in doubt for these files
/vesta:contractWhat was agreed to be built, and whether it has been
/vesta:decidedWhat you have decided in this project, and whether the code honours it
/vesta:defectsThings in this repository worth fixing, found without being asked
/vesta:doesWhere a kind of work is done here, asked in ordinary words
/vesta:driveRun until the agreed work is done, and know when that is
/vesta:elsewhereHow another project does a kind of work
/vesta:functionThe named functions of this project — list, show, define, brief, record, judge
/vesta:heldWhat Vesta is holding on disk, and what of it is dead
/vesta:helpWhat Vesta is and what you can do with it
/vesta:honingWhether you're honing in on this change, or just going round again
/vesta:knownWhat has already been worked out about a definition
/vesta:learnConfirm which of your corrections are standing rules for this project
/vesta:meansWhat a definition is for, and what else does the same kind of work
/vesta:notedCatch a rule you have always just observed, so it only needs saying once
/vesta:prepareStart building this repository's graph, in the background
/vesta:procedureControl-flow templates recorded for this project — list, add, or validate
/vesta:projectsWhat other projects Vesta can be asked about
/vesta:sampleRun each test on a few records, and know whether a full run is worth it
/vesta:shapeWhat this repository is made of, before reading any of it
/vesta:statusWhether Vesta can answer about this repository yet, and what it holds
/vesta:touchesWhat a change to these files affects, and which tests cover it
/vesta:tutorialLearn Vesta a page at a time, on your own repository
/vesta:usedWhat Vesta has been asked, and what it saved
/vesta:usesWhere a definition is, what refers to it, and what it refers to
/vesta:versionOne version in every place it is written — report, set, or tag
/vesta:whyWhy it concluded that, and whether the reasoning has aged well
/vesta:wordsThe words this project uses, and how to change them
vesta-defectsDerives finders for the kinds of defect this repository's own users have pointed at, so the same problem is caught elsewhere without anyone asking. Use when `defects` reports few findings on a repository with real history, when the user asks what is worth fixing or cleaning up, after a user rejects
vesta-domainNames what work a repository performs and binds its definitions to those names, so later questions asked in the language of the work reach code that shares no vocabulary with them. Use when a repository is new to Vesta, when `does` or `means` report that it has not been read yet, when the user asks
vesta-rulesRecovers the standing rules a repository's user has stated in earlier sessions — naming conventions, structural constraints, decisions they made once and expect to hold — and writes checks for them. Use when `decided` reports that nothing has been judged yet, before making a substantial change to an
vesta-specTurns what somebody asked for into a contract that can be built against and checked — behaviours phrased so a machine can tell whether each is met, the constraints they stated, and everything else inferred silently. Use when a user asks for something to be built and there is no agreed contract yet,
sidecarruns: ${CLAUDE_PLUGIN_ROOT}/bin/vesta-sidecar
${CLAUDE_PLUGIN_ROOT}/hooks/notice.sh
${CLAUDE_PLUGIN_ROOT}/hooks/inject.sh
${CLAUDE_PLUGIN_ROOT}/hooks/instead.sh
${CLAUDE_PLUGIN_ROOT}/hooks/keep-going.sh
${CLAUDE_PLUGIN_ROOT}/hooks/interrupted.sh
Matt Pocock's agent skills for real engineering (grilling, spec/ticket flows, TDD, code review, domain modelling and more).
39 skills
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
Automated code review for pull requests using multiple specialized agents with confidence-based scoring to filter false positives
1 command
Statically analyze a local JS/Electron app you're authorized to study, with file+line evidence, and build an original reimplementation of what you find. Experimental. Phase 1: JS/Electron static analysis. Phase 2: native ELF/PE/Mach-O container inspection. Phase 3: .NET assembly metadata. Phase 4: EVM bytecode inventory. Phase 5: CUDA fatbin, cubin and PTX inventory. Parses, never executes. Dynamic analysis is a future phase, not yet implemented.
1 skill · 1 command · 1 agent
Use Alibaba Open Code Review from local Codex.
2 skills
Code intelligence powered by a knowledge graph. Provides execution flow tracing, blast radius analysis, and augmented search across your codebase.
12 skills · 1 MCP server · hooks
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.