Apply Go community idioms for API and package design, error and concurrency patterns, naming (initialisms, stutter, receivers), generics vs interfaces, and Go code review — including PR or diff review, questions about "the Go way", pointer vs value receivers, channels vs mutexes, and building Go language tooling…
A software architecture review workflow that scans a codebase for structural risks and measures code quality. It checks issues such as overly complex code, repeated knowledge, changes spreading across many files, circular dependencies, and distorted domain models.
Run parallel multi-agent code review via Solo MCP — replicates the counselors tool (https://github.com/aarondfrancis/counselors) without depending on claude -p. Use when the user asks for "counselors", "second opinion", "panel of experts", "parallel review", or "multi-agent analysis" — fan the same task out to several…
Reviews Zod dependency upgrades for PatternFly MCP—maps release notes to codebase usage, runs tests, and writes a dated update report with impact tables and prioritized fixes. Use when bumping zod, on review zod, zod upgrade, zod integration review, assessing Zod breaking changes, generating a zod update report, or…
Primes an artefact-producing agent to separate what it intended, what it materialised, what it re-checked, and what remains unverified before it reports completion. Load for build-class tasks (code generation, evidence-pack emission, tool-wrapper generation, implementation work whose claims can be re-tested against…
Audit steam-games-mcp — build/test/lint gate, live MCP tool edge-case sweep (input validation, SteamID64/vanity/appid edge cases, key-gating), and source-level code review. Use when asked to test/audit the published or just-fixed steam-games-mcp package, hunt for bugs/edge cases, or repeat "the same kind of testing as…
Drift doc-to-code anchor conventions. Use when editing code that is bound by drift docs, updating docs, working with drift.lock, or when drift check reports stale anchors.
Backend security auditor for Django and DRF on an OWASP Top 10 (2025), API Security Top 10 (2023), and ASVS 5.0 foundation. Use when backend code is written or reviewed and touches authentication, sessions, cookies, JWT, OAuth2/OIDC, API keys, password hashing, permissions, access control, IDOR, SSRF, path traversal…
Use when a full GitHub repository URL (github.com/owner/repo) appears in conversation, when the user asks to check, review, or analyze a GitHub repo, or when the user runs /gitgauge. Does not trigger on npm packages, file paths, org pages, or issue/PR links.
Before you execute a drafted plan/spec/design doc, run a multi-agent adversarial cross-review to surface the flaws that cause downstream rework, aggregating "evidenced, cross-family-verified" objections into a verdict. Use when the user asks to "review this plan/spec", "can this approach be executed", "poke holes /…
Authors and executes git work end to end — Conventional Commits messages, pull-request content, release notes, and pull-request review, plus the repository operations an engineer runs daily: branching, rebasing, squashing, cherry-picking, reverting, merge-conflict resolution, stashes, tags, remotes, and recovery…
Review React, Next.js App Router, TypeScript, Tailwind CSS, shadcn/ui, TanStack Query, and frontend UI code. Use when reviewing a PR, branch, diff, page, component, hook, Server Action, route handler, or API client; debugging frontend behavior; assessing production readiness; or checking runtime bugs, client/server…
Drive a published spec to verified, pushed completion through a resumable backlog, worktree-isolated parallel builds under a lazy-senior-dev ladder, gate-first review, a milestone reviewer, and a final adversarial teardown. Use when the user invokes /ship, asks to build out a spec autonomously, or resumes a ship run.
Run an independent security audit of this repository before trusting it. Use when the user asks whether this project is safe, what it sends over the network, what it does to their computer, whether it is malware or spyware, or asks for a security review of this codebase.
Use when the user asks to audit a plan, document, diff, website finding, or implementation proposal with ChatGPT using Pro reasoning effort through Chrome - starts automatically after invocation, packages codebase/project context ChatGPT cannot see, runs up to 5 review rounds until accepted, verifies Effort Pro and…
Review a concrete code or configuration change through failure-mode, maintainability, and trust-boundary lenses, then return evidence-backed Markdown and a machine-verifiable JSON verdict.
Audit a codebase end to end and emit validated JSON plus remediation MDX, or review one diff for non-obvious blast radius with explicit safety facts and a compiled merge proof gate. godaudits fingerprints the repository, detects six project forms, validates Pillars 1.1 and arc-ready artifacts, evaluates 437 checks…
Autonomous, loop-until-clean diff refinement engine. Iteratively burns down feature and refactor diffs by deleting dead code, flattening empty abstractions, and enforcing strict layer boundaries (Sink & Lift). Every change is verified against tests. Use when asked to "crucible", "refine until clean", "burn down diff"…
★not rated 4 1mo agoA86 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: