All categories
Code Review & Quality
Code review, refactoring, debugging, maintainability, and engineering quality
- 15,938
- 665
Security grades appear on each card once the skill has been scanned. Newly imported skills may briefly show without a grade until the backfill job runs.
Open in full browserBrowse code review & quality skills
Showing 15,193–15,216 of 15,938 skills
- HardenHardens error handling, network failure recovery, and edge case resilience across the product. This skill should be used when the user asks to "harden error handling", "add resilience", "handle network failures", "add retry logic", "add circuit breakers", "handle edge cases", or "improve error recovery" — or when the transmute-pipeline agent reaches Stage 6G of the pipeline.Votes: 0GitHub stars: 4
- Review PrPre-PR review catching GitHub Copilot patternsVotes: 0GitHub stars: 16
- HardeningAudit and harden any repository with standardized quality gates, hooks, and scriptsVotes: 0GitHub stars: 16
- Process Pr ReviewsUse when the user asks to process, triage, fetch, view, count, list, or resolve review feedback in a GitHub PR. Supports both CodeRabbit and Codex review workflows. In this workflow, “real review feedback” is strictly defined as actionable inline comments; for CodeRabbit, exclude review summaries and nitpicks, and for Codex, exclude review summary cards and use PR main-thread reactions only as status signals.Votes: 0GitHub stars: 3,264
- Conductor DefectFix bugs reported by humans from a BUG.md file. Takes an application name (mandatory), version (optional — supports single version, comma-separated list, "all", or omit for all), and module (optional), resolves the context folder automatically from root-level application folders. When multiple versions are provided (or "all"/omitted), versions are processed SEQUENTIALLY in ascending semver order — all bugs from version N are fully resolved before version N+1 begins. Tags untagged bugs, cr...Votes: 0GitHub stars: 3
- OptimizingUse when optimizing a bundle-plugin or single skill — improving descriptions, reducing tokens, fixing audit findings, restructuring workflows, adding skills to fill gaps, or iterating on user feedbackVotes: 0GitHub stars: 230
- AuditingUse when reviewing a bundle-plugin for structural issues, version drift, skill quality, workflow integration, or security risks — before releasing, after changes, or after adding skills. Auto-detects scope (full project vs skill vs workflow)Votes: 0GitHub stars: 230
- Code ReviewReview code for quality, bugs, security issues, and suggest improvements. Use when asked to review, audit, or improve code.Votes: 0GitHub stars: 209
- GrillUse when the user wants a plan, design, or architecture stress-tested through relentless questioning until reaching shared understanding — even if they don't say "grill" explicitly. Any request to challenge, probe, or poke holes in a plan qualifies. Does homework first — explores the codebase, researches trade-offs, ranks options with pros/cons — then asks surgical questions about what's genuinely ambiguous. Resolves each branch of the decision tree one-by-one, surfacing contradictions, hidde...Votes: 0GitHub stars: 3
- ReviewUse when user invokes /review to review code changes. Also triggers on "review my code", "check this PR", "look at my changes". Accepts a PR number (e.g. /review 123), a path filter (e.g. /review src/auth/), or no argument (reviews current branch vs base). Produces structured per-file review with severity labels, cross-file analysis, and an overall verdict. Do NOT use for explaining what code does — use /explain instead.Votes: 0GitHub stars: 9
- Pr SweepUse when you want to sweep all open pull requests across all repos, triage their status, run code reviews on unreviewed PRs, merge what's ready, fix quick blockers, and produce a full status report. Trigger when the user says "check my PRs", "close out open PRs", "what's the status of my PRs", "sweep my PRs", "PR sweep", "pull request sweep", or wants a cross-repo PR status report. Future: pairs with the loop skill for ongoing automated PR management.Votes: 0GitHub stars: 9
- Invest DoctrineAudit the doctrine files themselves — VECTOR.md, CLAUDE.md, ARCHITECTURE.md — for completeness, internal consistency, cross-document contradictions, and drift from the actual codebase. Run this before invest-architecture. The doctrine must be sound before you enforce it.Votes: 0GitHub stars: 7
- Invest BackfillSurvey an existing codebase and generate Investiture doctrine files — VECTOR.md, CLAUDE.md, ARCHITECTURE.md — by combining Investiture defaults with patterns inferred from the project. Run this once on a project that does not yet have doctrine. Then run invest-doctrine to validate what was generated.Votes: 0GitHub stars: 7
- Invest ArchitectureAudit the project structure against ARCHITECTURE.md. Reads YOUR doctrine at runtime — layers, naming, stack, conventions — and checks the codebase against what YOU declared. Not a preset. Your rules, enforced.Votes: 0GitHub stars: 7
- HardenImprove interface resilience through better error handling, i18n support, text overflow handling, and edge case management. Makes interfaces robust and production-ready.Votes: 0GitHub stars: 7
- AuditPerform comprehensive audit of interface quality across accessibility, performance, theming, and responsive design. Generates detailed report of issues with severity ratings and recommendations.Votes: 0GitHub stars: 7
- RefineUse after a feature's code is implemented and passing, to clean up the changed code before verification. Triggers — "/engineer.refine", "refine this code", "clean up the feature", "refactor what we built".Votes: 0GitHub stars: 150
- FixUse to drive a bug fix from first report through close, with a "why didn't we catch it?" loop at the end. Triggers — "/engineer.fix", "a bug came in", "this is broken", "a user reported X", "there's a defect", "we have a regression", "this needs a fix", "another report", "more issues", "still failing", "validation failed again", "another bug", "next defect", "more fixes".Votes: 0GitHub stars: 150
- Arch CheckUse to check a feature's code against the charter's architecture rules — dependency layering, cycles, forbidden patterns, file naming, file size. Triggers — "/engineer.arch-check", "architecture check", "check architecture fitness", "does this follow the charter", "check layering".Votes: 0GitHub stars: 150
- Wjs Auditing ProjectUse when the user asks to audit what's wrong with a project, "make it right", "看看项目出了什么问题", "为什么用户的需求还没上线", "为什么没提交App Store", "为什么没新build", or wants a holistic state-of-the-project check covering unmerged branches, stalled PRs, failed GitHub Actions, stale builds, plan drift (TODOS.md / ROADMAP), unreleased commits, and log errors. Runs read-only investigation, presents a grouped checklist, fixes only after explicit user confirmation. Aware of the Cathier iOS app workflow (Xcode + fastlane +...Votes: 0GitHub stars: 128
- Github Review PrReview GitHub pull requests with detailed, multi-perspective code analysis using parallel subagents. Use this skill whenever the user wants to review a PR, asks for code review on a pull request, mentions "review PR", "check this PR", "look at pull request", or references a PR number or GitHub PR URL. Do NOT use for local uncommitted changes — this skill only reviews pull requests on GitHub.Votes: 0GitHub stars: 1,656
- GraphManage code knowledge graphs via code-review-graph (CRG). Build, update, and check status of project code graphs stored in .code-review-graph/graph.db. Use when: (1) user says "build graph", "update graph", "graph status", "/graph", (2) Harness init detects CRG, (3) preparing to use /explore commands. Gracefully degrades if CRG is not installed.Votes: 0GitHub stars: 265
- Surgical EditUse this skill on EVERY Edit, Write, or code-modification tool call. Enforces minimum-diff discipline — only touch files listed in the plan's in-scope list, only modify functions listed in the plan's in-scope functions, never modify adjacent functions, never refactor or rename unrelated code, never "fix while you're here". Unrelated bugs get logged to the follow-ups file, not fixed inline. This skill is the primary mechanism for the project's core rule "only touch code that needs to be modifi...Votes: 0GitHub stars: 3
- Minimal CodeUse this skill alongside the build skill to resist over-engineering. Enforces YAGNI (no speculative features), KISS (the simplest thing that could possibly work), and DRY-when-it-actually-repeats (not DRY-in-advance). Prefer standard library over new dependencies. Prefer editing existing code over creating new files. Prefer adding one function over adding one class. Prefer flat over nested. Trigger proactively whenever Claude is tempted to introduce an abstraction, a new dependency, a new mod...Votes: 0GitHub stars: 3