19,479 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.
Find duplicate functions and eliminate them so they stay gone. Triage tl dupes output by tier, apply the right consolidation pattern, and lock the win with a duplication-ratchet test. Use when asked to dedupe, remove duplication, consolidate copy-paste, clean up repeated helpers, or act on tl dupes output.
Evaluate repository or project code quality and produce an evidence-based scorecard. Use when asked to review code quality, score a project, assess maintainability, inspect technical debt, evaluate architecture/readability/refactoring health/engineering practices/code smells, compare project quality, or prepare a…
Use when working in a repository that has jjj initialized (a .jj/jjj-meta directory), or when coordinating several agents on shared work — tracking problems, proposing competing solutions, critiquing them, and reaching decisions that survive history rewrites. Also use when asked to set up multi-agent collaboration…
Multi-angle project review covering expert audits, visitor comprehension testing, task-completion smoke tests, and adversarial nitpick passes. Use when you want a thorough pre-launch review or a targeted quality check from any angle.
★not rated 13
changed 5d agoA
tokens not measured
originalMIT
Use when requesting a code review before pushing changes. Pre-commit verification pipeline — static security scan, baseline-aware quality gates, independent reviewer subagent, and auto-fix loop. Use after code changes and before committing, pushing, or opening a PR.
A code-review procedure for Python, JavaScript, and Go programs. It checks security, performance, maintainability, naming, error handling, and testing.
Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.
Musk 5-step engineering algorithm. Primarily for reviewing and cleaning up existing systems. Apply in strict order: question requirements, delete parts, simplify, accelerate, automate. Bias toward deletion. Never advance to a later step until earlier steps are visibly complete.
Reserved-string and numeric-coercion check, inspired by the Big List of Naughty Strings. Finds where literal "null", "undefined", "None", "NaN", "proto", "NO", 1E02, 0x10, -0, or a 17-digit ID become a blank field, a wrong number, or a crash. Types each case into a live test environment's forms and submits it…
Reviews pull requests for security vulnerabilities, logic bugs, data loss risks, and API misuse. Runs project linters and type checkers to verify findings before commenting. Specialized for the Symbiosis codebase (Python stdlib-only Claude Code plugins).
Run code, architecture, systems, or proposed changes through a panel of world-class engineering perspectives. Each panelist reads the ACTUAL source files before judging. Use this skill whenever the user asks to: review code quality, get expert opinions, assess architecture decisions, evaluate a refactor plan, critique…
Adversarial validation for all stages. Detects fabrications, identifies analytical flaws, challenges assumptions, makes approval decisions. Seeks problems rather than confirming quality. Does NOT complete deliverables or fix issues.
Radical-simplicity coding guidelines distilled from George Hotz's public philosophy. Use when writing, reviewing, refactoring, or porting code — to remove before adding, collapse duplication, keep interfaces narrow, and look at what code actually does instead of assuming.
MCP server "unified-diff-mcp" as configured in gorosun/unified-diff-mcp. Launched with bun /Users/username/projects/unified-diff-mcp/src/index.ts. Needs 5 environment variables to run.
Senior-QA review of a code change before you ship it. Sizes the diff, then launches QA reviewers — a regression hunter ("does this break anything that already worked?") and a change reviewer ("does this actually do what it claims, including edge cases?") — and consolidates ONE evidence-based SIGN OFF / SIGN OFF WITH…
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: