17,691 mods in this category, of every kind an
agent can take. Each one carries what it costs per session, what the
scan found, and whether it is the original.
The house Rails style, distilled from 37signals practice (Campfire, Fizzy, DHH's reviews). Use for all Rails coding, refactoring, and code review so architecture, naming, and safety standards stay consistent; fires on work touching models, concerns, controllers, routing, REST, authorization, dependencies, naming…
Runs a structured rigor check over code before it ships, with a specific mode for AI-generated output. Covers problem framing, edge cases, failure modes, explainability, and AI-specific failure patterns — hallucinated APIs, plausible-but-wrong library behavior, tests that mirror the code, defensive scaffolding that…
Review a GitLab Merge Request using the ai-review CLI. Fetches the MR diff, analyses it as a senior software engineer, produces structured inline comments by severity, and optionally posts them back to GitLab. Use when the user wants to review, analyse, or post feedback on a GitLab MR.
Stack-agnostic coding agents and orchestrator skills for feature planning, PR review, design review, PR batching, issue triage, simplification, codebase mapping, and installing the agents on a periodic schedule.
Use when writing, reviewing, or refactoring Java code to enforce baseline conventions for imports, nullability, immutability, exceptions, resource handling, naming, and concurrency.
Apply Pragmatic Programmer principles to raise code quality during planning and multi-class generation. TRIGGER AUTOMATICALLY (without user asking) whenever: (1) entering plan mode, (2) about to generate or modify 2+ files/classes in a single task, (3) creating new services, controllers, DTOs, or model classes, (4)…
Transform any software repository into a contributor-friendly, production-ready open source project. Analyzes repo health, generates documentation, creates GitHub community files, identifies contribution opportunities, and produces a readiness report. Agent-independent and technology-agnostic.
Development practices and workflows for quality-driven software engineering. Provides TDD, session completion, molecular task execution with formula-based atom graphs, multi-agent code review, entity test remediation, obligation-driven test derivation, test source-of-truth auditing, and obligation reclassification.…
★not rated 2 1mo agoA
tokens not measured
originalMIT
Walk through pull request review comments one at a time with the user before making or resolving changes. Uses one orchestrator agent that spawns a fresh subagent per comment with isolated context. Presents click-to-choose polls (AskQuestion) at every decision point so the user picks an approach instead of typing. Two…
Respond to code-review comments on a GitHub PR end to end — fetch unresolved threads, triage real reviewers from CI/bot noise, fix or reason-and-push-back on each, then get one go-ahead on the real diff before pushing, replying to every thread, and resolving the ones no human is waiting on. Use when a PR has review…
Run a Gauntlet Loop on a goal: split work into independent pieces, fan out builder + fresh-context critic pairs, score each piece out of 10 against a concrete bar (reference and/or acceptance criteria), and keep looping until every critical piece is 10/10 or the user stops. Use when the user runs /gauntlet, or says…
Safely refactor .NET / C# code at Senior Engineer level — diagnose code smells, classify risk (SAFE/RISKY/DANGEROUS), check the test safety net (or add characterization tests first), apply smallest-change-at-a-time for one smell, preserve behavior, match project convention. Use when the code being rewritten…
Use for expert engineering judgment, "X mode", seasoned/staff/principal standards, robust architecture, security/performance/reliability/scalability scrutiny, optimization review, rigorous implementation/release discipline, or implementation with implement-release-flow. A rigor overlay for design, testing, reviews…
Manage the user's external GitHub PR workflow from project name to fork/clone, multi-agent bug hunting, PR-value validation, formal PR creation, reviewer feedback, and detailed PR comment section expansion. Use when the user asks to fork or clone a GitHub project, find small fixable PR opportunities, launch…
Decide how much review a change has earned, before reviewing it. Selects quick, standard, or deep from stated signals (reviewable changed lines, directory spread, trust-boundary risk flags, blast radius, documentation-only scope), reports the signal table and the rule that fired, then runs house-review at the selected…
A workflow for handling comments left by reviewers on a GitHub pull request, which is a proposed code change awaiting review. It groups comments and suggests whether each needs action, clarification, or no change.
Read-first wrapper around the GitHub REST API — one-call PR/branch overviews (state + checks + reviews + runs), name-resolved PRs and issues, --wait on async flows, --json on lists. Zero token leakage. One write: pr comment.
★not rated 2 4mo agoA
tokens not measured
originalMIT
Use when reviewing code adversarially or building production-bound features where rigour matters more than speed. Required for code reviews ending in a verdict (PASS/HOLD), when verifying that "tests pass" actually proves a feature works end-to-end, before closing findings as non-issues, before signing off your own…
Open a pull request the safe way and handle review comments on it. Use when creating a branch, pushing work, opening a PR, or working through bot/human review threads. Encodes branch hygiene, an explicit-refspec push that can't accidentally advance main, "open the PR but never merge — bots/maintainer review," and the…
Addresses comments made on the GitHub Pull Request tracking changes of the current branch. What this does is read all Pull Requests comments addressed to the agent, improve or fix the code based on those comments, and reply too each one of those comments. Use this when the user is asking you to address the comments…
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: