Perform architecture- and maintainability-focused code reviews. Use when the user asks for code review, style review, refactoring feedback, or review of architecture, cohesion, coupling, TypeScript rigor, naming, tests, responsibility boundaries, or unnecessary abstractions.
Chaos agent for skills — a vigilance-training layer that keeps humans reviewing AI output instead of rubber-stamping it. Consult this skill on EVERY substantive request (code, analysis, writing, SQL, configs, explanations — anything with a checkable answer). 95% of requests get your genuine best work; a deterministic…
Design and review Rails applications using layered architecture principles from "Layered Design for Ruby on Rails Applications". Use when analyzing Rails codebases, reviewing PRs for architecture violations, planning feature implementations, or implementing patterns like authorization, view components, or AI…
Gate whether a fix or existing contributor PR is the right thing to build. Use before implementation when a defect has multiple solution shapes or changes a contract, especially session state, long-lived process configuration, restart or reuse behavior, fixes to prior review findings, and decisions to adopt, absorb…
Multi-angle code review that adapts to what is being reviewed — a mid-flight worktree increment, a full PR before production, a merge-window integration sweep, or a security-only pass. Findings are scored, adversarially refuted, widened to the same defect elsewhere in the codebase, and reported to the native review…
Plan, install, inspect, update, or roll back Rootloom Personal Core in a user's Codex home. Supports Skills-only, guidance, and the recommended personal preset. Use when the user explicitly asks for a Rootloom setup plan, installation, configuration, bootstrap, repair, audit, status, update, reduction, rollback, or…
REST API design patterns including resource naming, status codes, pagination, filtering, error responses, versioning, and rate limiting for production APIs. Also lazy-loads api-versioning.md / contract-testing.md / schema-evolution.md / deprecation-lifecycle.md content migrated from rules/common/ on 2026-06-02.
Review codebase or design for modularity problems and produce actionable improvement recommendations. Also guides design of new modular boundaries from functional requirements. Inspired by Vlad Khononov's balanced-coupling model and golden-age-of-modularity principles. NOTE: Full upstream plugin at…
Use when an agent should work with Lifeblood's MCP semantic-code tools: analyzing C# or Unity workspaces, querying symbols/dependencies/blast radius/file impact/test impact, checking architectural invariants, validating edits with compilecheck/diagnose, or choosing the right Lifeblood tool instead of grep-style…
Verify agent code against organizational policies and best practices. Trigger this skill when the user says something like "verify my agent", "review agent code", "check compliance", "audit my agent", "check my agent against rules", or "validate agent implementation".
Structured GitHub PR/diff review across correctness, security, tests, and architecture with severity ratings. Use to review a PR or pull request. (Built-in /code-review for a quick working-tree diff; this is the full multi-dimension PR pass.).
Run a diff-scoped code audit for architecture, dead code, and test quality. Uses the change from main to focus feature reviews; request a repository audit for whole-codebase discovery.
Audit and harden the brain-mcp repository with Hermes Agent. Use when Codex needs to inspect this repo for reliability, orchestration, or maintainability weak spots; run a read-only Hermes audit; implement one or two bounded fixes locally; validate the result; and then commit and push only the intended changes.
A set of rules for reviewing, generating, and refactoring Java code against Alibaba Java Coding Guidelines, a published style and quality guide. It also covers related Spring, MyBatis, Maven, SQL, database, logging, error-handling, and security code.
Use when the user needs to compress, condense, or summarize lengthy content while preserving ALL critical details. Triggers: "compress this", "make it shorter but keep everything", "create a cheat sheet", "dense summary", "reference format", "compact version", "information-dense". NOT for casual summaries—only when…
Review embedded C/C++ firmware changes using fw-context MCP tools. Three-phase workflow: (0) create a review plan from the diff, (1) structural verification via callers/callees/types, (2) logic review across 9 embedded-specific domains. Takes priority over generic review skills for C/C++ code. If project has a local…
Goal-first guardrail for planning, changing, testing, reviewing, or removing code and engineering artifacts. Preserve observable outcome, canonical ownership, risk, validation, and honest evidence without scope drift. Not for conceptual questions unrelated to a codebase.
Conducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensions before it enters the main branch.
Run structured AI code review as an advisory closeout gate for local diffs, PR branches, or commits when the user asks for autoreview, Codex review, second-model review, or pre-ship validation.
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: