All categories
Code Review & Quality
Code review, refactoring, debugging, maintainability, and engineering quality
- 14,947
- 623
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 14,353–14,376 of 14,947 skills
- Dotnet Techne Crap AnalysisUse when you need CRAP score and coverage risk analysis to find high-risk code before refactoring or release. Keywords: CRAP score, risk hotspots, cyclomatic complexity, test coverage gaps, coverage threshold.Votes: 0GitHub stars: 12
- Dotnet Techne Code ReviewUse when reviewing PRs/diffs/branches/documents for .NET quality, correctness, performance, security, data access, messaging, and observability. Includes adversarial critical-thinking mode for skeptical/cynical review requests. Keywords: code review, review PR, review diff, critical review, cynical review, adversarial review, production readiness, low GC, AOT, security review.Votes: 0GitHub stars: 12
- Build And TestInstall dependencies, run type checking, lint, tests, and build the project. Use after making code changes to verify nothing is broken.Votes: 0GitHub stars: 67
- Meta RulesAgent and skill writing rules for Claude Code plugins. Enforces anti-bloat constraints, token limits, and quality standards for all auto-generated improvements.Votes: 0GitHub stars: 2
- Receiving Code ReviewUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationVotes: 0GitHub stars: 9
- Code RefactoringCode refactoring patterns and techniques for improving code quality without changing behavior. Use for cleaning up legacy code, reducing complexity, or improving maintainability.Votes: 0GitHub stars: 9
- Measure Before OptimizePre-change measurement gate for perf-sensitive functions. Use BEFORE modifying any function that has a pytest-benchmark test, appears in a performance baselines file, or is flagged as a hot path in CLAUDE.md / AGENTS.md. Captures baseline median and p95, verifies the change does not regress beyond a configurable threshold, reports the delta. Peer skill to optimization-audit — this one is pre-change; that one is retrospective.Votes: 0GitHub stars: 3
- Final ReviewPre-commit quality gate — reviews all code and documentation for consistency, best practices, and completeness, then generates or updates the C4 architecture diagram. Use before committing, or when you want a thorough quality check of the project. Triggers on phrases like "final review", "pre-commit check", "review everything before commit", or "make sure everything is up to date".Votes: 0GitHub stars: 3
- PlanningSet up pre-implementation discipline + audit routing for a project with regular multi-module changes. Authors a pre-flight agent that maps integration points, parallel paths, and cross-boundary surfaces — plus an audit-routing rule that orders which agent fires for which question. Invoke /dotclaude:planning in any project where "we shipped feature X and broke unrelated thing Y" has happened more than once.Votes: 0GitHub stars: 2
- CodingSet up coding hygiene + voice discipline for a project. Authors a tailored kit of code-review agent, decomposition skill, file-size + voice rules, and edit-time hooks — derived from the project's stack, its actual file-size distribution, the bug classes visible in git history, and any project-specific voice. Invoke /dotclaude:coding in any project root with source code.Votes: 0GitHub stars: 2
- ReviewReview pending capsule drafts one-by-one — scan for PII, then push, skip, or delete each draft.Votes: 0GitHub stars: 2
- Consensus ToolsRun consensus-loop deterministic analysis tools via CLI — code_map, dependency_graph, audit_scan, coverage_map, rtm_parse, rtm_merge, audit_history, fvm_generate, fvm_validate. Use this skill whenever you need codebase analysis (symbol index, dependency DAG, pattern scan, coverage), RTM operations (parse, merge, query), or FVM operations (generate matrix, validate against server) — even if the MCP server is not configured. This skill replaces mcp__plugin_consensus-loop_consensus-loop__* tool ...Votes: 0GitHub stars: 15
- Consensus LoopGuide for writing evidence packages for the consensus-loop watch file. Use when preparing code review submissions, structuring feedback evidence, or addressing audit rejections.Votes: 0GitHub stars: 15
- AuditRun a consensus-loop audit manually — Codex reviews pending trigger_tag items in the watch file. Use when you want to trigger an audit without editing the watch file, re-run a failed audit, or test the audit prompt.Votes: 0GitHub stars: 15
- NukeThis skill should be used when the user asks to "nuke dead code", "find unused exports", "clean up imports", "find orphaned files", "detect circular deps", "cleanup codebase", "find unused packages", "remove dead code", "nuke this", "nuke unused", or needs comprehensive codebase hygiene analysis.Votes: 0GitHub stars: 110
- Refactor GuideWhen activated, analyze code and suggest refactoring improvements: - Extract repeated logic into functions - Reduce cyclomatic complexity - Apply SOLID principles - Improve naming and readability - Suggest design patterns where appropriate Provide before/after code examples for each suggestion.Votes: 0GitHub stars: 3,940
- ReviewPre-screen open pull requests: diff analysis, security scan, test coverage, breaking change detection, bot detection. Human approves all review comments. Use when asked to "review PRs", "check pull requests", "screen PRs", or "pre-review open PRs".Votes: 0GitHub stars: 3
- Navigating Gdlc Code MapsUse when exploring codebase structure or understanding module dependencies using the .gdlc file-level code index — finding which file exports a symbol, tracing import relationships, or getting oriented in an unfamiliar codebase. Triggers on: \"where is X defined\", \"what depends on Y\", \"show me the project structure\", getting an overview of the codebase, finding files by directory or language, or direct .gdlc file operations. NOT for reading or searching source code implementations, runni...Votes: 0GitHub stars: 3
- Managing GdlignoreUse when excluding files or directories from GDL scanning — generated code, node_modules, UI component libraries, or test fixtures that pollute code maps. Triggers on: 'ignore this directory', 'exclude from scanning', 'too much noise in GDL', '.gdlignore'. NOT for .gitignore management or general file filtering.Votes: 0GitHub stars: 3
- Managing Gdl RulesUse when creating, reviewing, or maintaining @rule records in rules.gdl files — provides format reference, quality criteria for what makes a rule worth writing, severity calibration, and the gdl_rules_for_file helper. Triggers on: rules.gdl files, 'add a rule', 'create a coding rule', 'enforce this convention', observing a strong codebase convention. NOT for @memory observations, .gdlm files, or general code review.Votes: 0GitHub stars: 3
- Sdd CheckInternal — Verify that generated code is consistent with its approved SDD specification. Automatically called by sdd-gen. Can also be invoked manually to detect drift after manual code changes.Votes: 0GitHub stars: 4
- Sdd AuditInternal — Comprehensive quality audit of generated code. Automatically called by sdd-gen after consistency check passes. Configurable via sdd.config.json.Votes: 0GitHub stars: 4
- HealthAudits agent config, instruction drift, hooks or MCP, and AI maintainability. Use when Claude, Codex, or Pi setup looks wrong. Not for application bugs or PR review.Votes: 0GitHub stars: 7,166
- CheckReviews diffs, PRs, release readiness, and publishing follow-through. Use when asked to review, triage issues or PRs, or ship. Not for debugging root causes or prose.Votes: 0GitHub stars: 7,166