Audit code against NASA JPL's Power of Ten rules, extended for AI-assisted development. Use when checking code for dangerous complexity, unsafe control flow, resource leaks, hidden side effects, missing validation, weak CI gates, AI-generated artifacts, or missing failure-mode tests.
Teaches an AI agent to use grafel MCP tools as a structural second pair of eyes during code review. Covers impact radius analysis, orphan detection, dead-end flow discovery, cross-repo consistency checks, and pattern violation spotting — with a per-change-type tool sequence, a severity rubric, and worked examples.
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…
Review this codebase against the prodcheck pre-production checklists — security, performance, scale, integrations and post-launch readiness. Use when asked to check whether a project is ready to ship, to audit an area before launch, or to work through a specific checklist. Produces evidence with file:line citations…
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.
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…
Auto-review pipeline — reads the full CEO, design, eng, and DX review skills from disk and runs them sequentially with auto-decisions using 6 decision principles. Surfaces taste decisions (close approaches, borderline scope, codex disagreements) at a final approval gate. One command, fully reviewed plan out. Use when…
CVE-oriented multi-agent code audit system. Use when user provides a git repository URL for vulnerability discovery with the goal of submitting CVEs. This skill orchestrates subagents to find exploitable vulnerabilities (RCE, SQLi, Auth Bypass, etc.), write weaponized POCs, and generate CVE-ready reports. ALWAYS use…
Check your work with a verification subagent that reviews diffs, runs builds and tests, and evaluates correctness. Read this file for instructions. Use when asked to "check work", "verify changes", "self-verify", "/check-work", "/check", "/verify", or "/self-verify".
This skill lets you run the coding-review-agent-loop orchestration directly inside an interactive Claude Code session, without calling claude -p for Claude turns.
Post-implementation quality gate that reviews changes, fixes small issues (scout rule), creates tasks for medium issues, and generates analysis for large issues.
Review GitHub pull requests using gh CLI and the GitHub API. Use when asked to review a PR, inspect PR changes, or choose approve/comment/request-changes.
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.
README-ROAST — Your README is lying. 8 savage personas roast your project's README with a Honesty Score, 3-5 punchy observations, a tweet-ready one-liner, and a shareable badge. Short. Funny. Accurate. Invoke with /readme-roast on any repo. Screenshot the output. Share it. Let the badge spread.
A code-review procedure for checking a change from its commit history through its final tests. It covers scope, changed files, behavior, security, performance, and missing tests.
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.
Use this skill when conducting or improving code reviews. Provides structured review processes, conventional comments patterns, language-specific checklists, and feedback templates. Ensures consistent, constructive, and thorough code reviews across teams.
Open interactive diff review UI in browser for current changes.
★not rated 11 5mo agoA13 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: