Establishes and enforces engineering conventions, quality gates, and architectural guardrails for a codebase, and onboards itself via /guider init. Use whenever the user wants to set up or apply project standards: conventions, naming, linters, formatters, pre-commit hooks, secret scanning, CI gates, data integrity…
Reviews and grades an agent skill directory (SKILL.md plus supporting resources) for specification compliance, clarity, token efficiency, safety, robustness, and portability. Produces an evidence-cited weighted score and grade, P1/P2/P3 findings with minimal patch text, and a machine-readable verdict with structured…
Scan React codebase for useEffect anti-patterns (derived state, event logic in effects, effect chains, prop-driven resets, missing cleanup, parent notifications, etc.) and propose idiomatic fixes. Based on React's "You Might Not Need an Effect" guide. Use when asked to audit, review, or clean up useEffect usage.
Review code for security vulnerabilities, performance issues, and coding best practices. Activate when the user asks to review code, check code quality, give feedback on code changes, or audit a file.
A process for discussing a GitHub issue with its author or maintainers, agreeing on a solution, and later reviewing the related pull request. GitHub issues are online records for bugs, requests, and proposed work.
A pull-request restart workflow for replacing a messy review with a new pull request containing one clean commit and a summary of the earlier discussion.
Read a partner's agent codebase, score it across the 12-dimension catalog, and emit an evidence-cited markdown plus branded scored HTML report. Use for a first-touch audit: assess/review/audit our agent, where to improve, spot low-hanging fruit, an honest read of what's weak, what Ratel would notice, or…
A code-review procedure for Python, JavaScript, and Go programs. It checks security, performance, maintainability, naming, error handling, and testing.
Orchestrate Codex subagents for complex multi-part coding work. Use when independent exploration, review, tests, or bounded implementation streams can run in parallel; do not use for small sequential tasks or tightly coupled concurrent edits.
Turn a GitHub pull request into an interactive review map with AI insights, reviewed in the browser. Use when the user asks to review, map, or visualize a PR.
Multi-agent panel review of a PR or current-branch diff. Three-model fan-out across Opus, Sonnet, and Haiku. Opus and Sonnet review for regressions, security issues, and bugs; Haiku reviews convention drift, naming, dead code, and comment quality. Discrete severity levels (nit, question, blocker). Sonnet confidence…
A code-review process in which one AI model reviews code produced by another model, or uses multiple review perspectives when only one model is available. The review mode is recorded and can be marked blocked when it cannot run.
Use for code verification, debugging, and deep code analysis without running tests. This skill should be used when the user asks to "verify my changes", "check my patch", "find the bug", "why does this test fail", "are these changes correct", "review this diff", or when analyzing code semantics that require tracing…
Use when the user asks for a deep review, full review, comprehensive review, production readiness assessment, full audit, multi-domain audit, "security and reliability and code review", or "review everything". Also use when the user explicitly requests performance review alongside the comprehensive request (e.g.…
Review the current diff against this team's conventions and invariants before it ships. Invoke with /prereview before opening a PR, or run as a pre-push gate.
Find architecture deepening, terminology, and semantic-symmetry opportunities in a codebase. Use for architecture or refactoring audits, tightly coupled or shallow modules, weak test seams, scattered domain concepts, overloaded names, or sibling workflows whose ownership and transitions drift unexpectedly. Do not use…
Triage and resolve review comments on a GitHub PR. Reads all comments, assesses each one, and presents a resolution table. The user can then approve, modify, or reject resolutions, and the agent applies the chosen changes.
★not rated 9 21d agoA50 tokens
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: