Use when reviewing one or more implementation plan documents against the design, spec, or brainstorm doc that initiated them, before the plan is executed, to verify alignment, completeness, feasibility, and grounding in real code.
Research a technology, tool, framework, concept, or methodology — or compare two or more of them — through a progressive flow: preliminary gist delivered immediately from web search, informed clarifying questions, then parallel subagent research synthesised into a conversational explanation or a written study guide.…
Resolves a Maven dependency coordinate, artifact name, or class name to real, readable Java source pulled from the local /.m2/repository -- extracting its -sources.jar when one exists, or decompiling just the needed class with CFR when it doesn't -- so a library's actual internals can be traced instead of guessed at.…
Generate a short, accurate kickoff prompt that a fresh session pastes to implement an already-reviewed plan after the planning session's context is cleared. Pins an exact baseline (git HEAD, clean tree, green tests) and carries only out-of-band context the plan itself does not. Use when the user says "handoff prompt"…
Create, refactor, review, and improve Agent Skills — portable skills for Claude Code, OpenAI Codex, or any other agent host, plus the Claude Code plugin components around them when authoring specifically for Claude Code. Use when the user wants to: turn a script into a reusable skill, create a skill from scratch…
Comprehensive PR/diff review across code quality, tests, comments, error handling, and type design, using six specialist checklists (references/specialists/) dispatched as subagents or worked through sequentially; also offers to simplify code after a passing review. Trigger when the user asks to review a pull request…
★not rated 2 1mo agoA100 tokens
originalMIT
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: