Lives inside packages/rpiv-pi/. The web-search-class agent's tools are provided by the rpiv-web-tools sibling. The Agent dispatch runtime comes from the third-party subagent extension that rpiv-pi declares as a wildcard ("") peer dependency.
Independent post-finalization code reviewer. Walks each slice code fence in a finalized artifact against three dimensions — code quality, codebase fit, actionability — and emits one severity-tagged row per finding (blocker | concern | suggestion). Use whenever a finalized plan or design needs adversarial vetting of…
Independent post-finalization coverage reviewer. Walks every ## Verification Notes and ## Precedents & Lessons entry in a finalized artifact and verifies each lands somewhere actionable — either reflected in a phase's ### Success Criteria: bullet or visibly addressed by the slice's emitted code. Emits one…
Finds relevant documents in .rpiv/artifacts/. The research equivalent of codebase-locator. Use when you need to discover prior research, designs, plans, or reviews that are relevant to the current task.
Adversarial finding verifier. Grounds each supplied claim against actual repository state and emits one FINDING | | row per input, with tags Verified / Weakened / Falsified. Tier: git-analyzer (+ bash for git show). Use whenever a list of code claims needs independent grounding before it is acted on.
Analyzes codebase implementation details. Call the codebase-analyzer agent when you need to find detailed information about specific components. As always, the more detailed your request prompt, the better! :).
Locates files, directories, and components relevant to a feature or task. Call codebase-locator with a human-language prompt describing what you're looking for. A "super grep/find/ls" tool. Reach for it when you would otherwise reach for grep, find, or ls more than once.
You are a specialist at finding code patterns and examples in the codebase. Your job is to locate similar implementations that can serve as templates or inspiration for new work.
Row-only patch auditor. Walks a patch against a caller-supplied surface-list and emits one pipe-delimited row per finding (file:line | verbatim | surface-id | note). Use whenever a diff needs evidence-only enumeration of matching patterns, with no narrative or severity.
Finds what connects to a given component or area: inbound references, outbound dependencies, config registrations, event subscriptions. The reverse-reference counterpart to codebase-locator. Use when you need to understand what calls, depends on, or wires into a component.
Pairwise peer-invariant comparator. Given (newfile, peerfile) pairs, tags each peer invariant Mirrored / Missing / Diverged / Intentionally-absent against the new file. Use when an entity parallels an existing sibling (aggregate, service, handler, reducer, repository) and the new file must be checked against the…
Finds similar past changes in git history: commits, blast radius, follow-up fixes, and lessons from related .rpiv/artifacts/ docs. Use when planning a change and you need to know what went wrong last time something similar was done.
Traces the scope of a research investigation. Sweeps anchor terms across the codebase, reads 5-10 key files for depth, and returns a Discovery Summary + 5-10 dense numbered questions that bound what the research skill should investigate. Use when a skill needs the discover-phase output without running a separate…
Per-slice adversarial verifier for incremental plan or design generation. Audits a just-generated slice against shared contracts, locked prior slices, target source files, and recorded constraints, then emits a structured Decisions / Cross-slice / Research summary. Use whenever a freshly-generated slice in a phased…
Do you find yourself desiring information that you don't quite feel well-trained (confident) on? Information that is modern and potentially only discoverable on the web? Use the web-search-researcher subagenttype today to find any and all answers to your questions! It will research deeply to figure out and attempt to…
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: