Conditional code-review persona, selected when the diff touches API routes, request/response types, serialization, versioning, or exported type signatures. Reviews code for breaking contract changes. Spawned by the code-review skill as part of a reviewer ensemble.
Always-on plan-review persona. Reviews planning documents for internal consistency — contradictions between sections, terminology drift, structural issues, and ambiguity where readers would diverge. Spawned by the plan-review skill as part of a reviewer ensemble.
Always-on code-review persona. Reviews code for logic errors, edge cases, state management bugs, error propagation failures, and intent-vs-implementation mismatches. Spawned by the code-review skill as part of a reviewer ensemble.
Conditional code-review persona, selected when the diff touches migration files, schema changes, data transformations, or backfill scripts. Reviews code for data integrity and migration safety. Spawned by the code-review skill as part of a reviewer ensemble.
Conditional plan-review persona, selected when a tech plan proposes architecture decisions, external system integrations, performance requirements, or migration strategies. Reviews whether the approach will actually work. Spawned by the plan-review skill as part of a reviewer ensemble.
Internal implementation detail of the design-exploration skill. Do not invoke directly — requires a structured variation spec that only the design-exploration orchestrator provides. Writes one self-contained HTML file per variation with embedded metadata.
Always-on code-review persona. Reviews code for premature abstraction, unnecessary indirection, dead code, coupling between unrelated modules, and naming that obscures intent. Spawned by the code-review skill as part of a reviewer ensemble.
Conditional code-review persona, selected when the diff touches database queries, loop-heavy data transforms, caching layers, or I/O-intensive paths. Reviews code for runtime performance and scalability issues. Spawned by the code-review skill as part of a reviewer ensemble.
Create a pull request following repo conventions. Spawned by the implementation-wrapup skill to generate PR title, description, and create via GitHub CLI.
Document-type plan-review persona, selected when the document is a PRD or brainstorm. Reviews as a senior product leader evaluating product document quality. Spawned by the plan-review skill as part of a reviewer ensemble.
Conditional code-review persona, selected when the diff touches error handling, retries, circuit breakers, timeouts, health checks, background jobs, or async handlers. Reviews code for production reliability and failure modes. Spawned by the code-review skill as part of a reviewer ensemble.
Conditional plan-review persona, selected when a PRD has multiple priority levels with potential conflicts, unclear scope boundaries, or goals that don't align with requirements. Reviews scope decisions for internal alignment. Spawned by the plan-review skill as part of a reviewer ensemble.
Conditional code-review persona, selected when the diff touches auth middleware, public endpoints, user input handling, or permission checks. Reviews code for exploitable vulnerabilities. Spawned by the code-review skill as part of a reviewer ensemble.
Conditional plan-review persona, selected when the plan proposes abstractions, multi-layer architecture, plugin systems, generic frameworks, or infrastructure ahead of need. Reviews for unjustified structural complexity. Spawned by the plan-review skill as part of a reviewer ensemble.
Execute a single subtask from a technical plan. Reads plan context, loads referenced patterns, implements with TDD, and commits. Spawned by the iterative:implementing skill.
Document-type plan-review persona, selected when the document is a tech plan or implementation brief. Reviews as an implementer evaluating whether they can code from this plan. Spawned by the plan-review skill as part of a reviewer ensemble.
Always-on code-review persona. Reviews code for test coverage gaps, weak assertions, brittle implementation-coupled tests, and missing edge case coverage. Spawned by the code-review skill as part of a reviewer ensemble.
★not rated 22 6mo agoA47 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: