All categories
Code Review & Quality
Code review, refactoring, debugging, maintainability, and engineering quality
- 14,948
- 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,281–14,304 of 14,948 skills
- Profile MemoryProfile memory usage in sidecar using Go pprof, system tools, and heap analysis. Covers identifying memory leaks, goroutine leaks, file descriptor accumulation, and CPU profiling. Use when investigating memory issues, profiling performance, debugging memory leaks, or diagnosing unresponsive plugins.Votes: 0GitHub stars: 1,086
- Coding PrinciplesCore behavioral principles: when to ask, when to push back, when to simplify, how to make surgical changesVotes: 0GitHub stars: 4
- Refactor<!-- Source: github/awesome-copilot --> <!-- Snapshot: 2026-03-20 --> --- name: refactor description: 'Surgical code refactoring to improve maintainability without changing behavior. Covers extracting functions, renaming variables, breaking down god functions, improving type safety, eliminating code smells, and applying design patterns. Less drastic than repo-rebuilder; use for gradual improvements.' license: MIT ---Votes: 0GitHub stars: 13
- Code ReviewUse when reviewing AI-generated code for architectural quality, design patterns, and engineering practicesVotes: 0GitHub stars: 13
- Sample ProductReview git commits for quality, clarity, and best practices before pushing. Checks commit message format, diff size, test coverage signals, and common mistakes. Use when reviewing commits, before pushing, when asked to "check my commits", "review changes", or "is this ready to push".Votes: 0GitHub stars: 25
- Code Health CheckRun a comprehensive codebase health analysis covering dead code, dependency freshness, test coverage gaps, security surface, and complexity hotspots. Produces a scored report with prioritized remediation. Use when the user asks to "check health", "audit the codebase", "code quality", or "technical debt".Votes: 0GitHub stars: 25
- ValidateRun MCS quality validation on products in workspace/. Three-tier system: MCS-1 structure, MCS-2 quality + anti-commodity, MCS-3 deep review. Returns scored reports with fix instructions. Use when: 'validate', 'check quality', or before publishing.Votes: 0GitHub stars: 25
- Wiki LintHealth-check the knowledge wiki — find orphans, broken links, missing frontmatter, contradictions, stale content, and statistical drift. Use when the user says "lint the wiki", "health check", or periodically for maintenance.Votes: 0GitHub stars: 139
- Code Health CheckPerform a comprehensive code health check on a directory. Use when the user asks to analyze code quality, find issues, or get a health report.Votes: 0GitHub stars: 1,091
- 00 Basic SkillReview code for quality, security, and best practices. Use when the user asks for code review, wants feedback on their code, mentions reviewing changes, or asks about code quality.Votes: 0GitHub stars: 1,091
- Remove DeadcodeRemove unused code from this project with ultrawork mode, LSP-verified safety, atomic commits. Triggers: remove dead code, dead code, cleanup, remove unused.Votes: 0GitHub stars: 69,843
- Code ReviewAnalyze pull requests and diffs for bugs, security vulnerabilities, performance issues, style violations, and test coverage gaps — producing structured, actionable feedbackVotes: 0GitHub stars: 76
- Code Review MeanCode review for MEAN stack apps. Use when reviewing backend (Express + MongoDB) and frontend (React) code for quality, security, architecture compliance, performance, and best practices.Votes: 0GitHub stars: 3
- System DesignSystem design and code review skill for fullstack Go+React apps. Use when designing architecture or reviewing code against design specifications.Votes: 0GitHub stars: 3
- Spectra DebugSystematically debug a problem using a four-phase workflowVotes: 0GitHub stars: 38
- ReviewReview code, specifications, or designs for quality, bugs, security, and best practices. Use when the user wants feedback on recent work, a pull request, or any artifact.Votes: 0GitHub stars: 14
- ConventionsShared conventions for the solopreneur workflow. Preloaded into agents via the skills frontmatter field.Votes: 0GitHub stars: 14
- Unslop ReviewRewrites code review comments so they read like a human teammate wrote them. Cuts corporate-AI throat-clearing ("I noticed...", "I was wondering if perhaps...", "It might be worth considering..."). Each comment is direct: location, the issue, a concrete fix. Use when user says "humanize review", "de-slop PR comment", "make this feedback sound human", "review this PR", "code review", "/review", "/unslop-review". Auto-triggers when reviewing PRs.Votes: 0GitHub stars: 153
- Unslop CommitRewrites commit messages so they sound like a careful human engineer wrote them. Strips AI/marketing slop ("comprehensive solution", "robust implementation", "leverage", "enhance", "seamlessly", "This commit..."). Keeps Conventional Commits format. Subject ≤72 chars (aim ≤50), imperative mood. Body only when "why" isn't obvious from the subject. Use when user says "humanize commit", "de-slop commit message", "make this commit sound human", "/unslop-commit", "/commit", "write a commit", or pas...Votes: 0GitHub stars: 153
- PrComprehensive PR/issue review - analyzes architecture, tests, identifies unrelated changes mixed in, drafts review comment or issue comment. Use when user asks to review a PR, check a PR, look at PR changes, or comment on an issue.Votes: 0GitHub stars: 483
- Caveman ReviewUltra-compressed code review comments. Cuts noise from PR feedback while preserving the actionable signal. Each comment is one line: location, problem, fix. Use when user says "review this PR", "code review", "review the diff", "/review", or invokes /caveman-review. Auto-triggers when reviewing pull requests.Votes: 1GitHub stars: 110,002
- Caveman CommitUltra-compressed commit message generator. Cuts noise from commit messages while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious. Use when user says "write a commit", "commit message", "generate commit", "/commit", or invokes /caveman-commit. Auto-triggers when staging changes.Votes: 1GitHub stars: 110,002
- A11y FixesResolve axe-core accessibility violations reported by a story under Vitest (addon-a11y), Playwright (.playwright/a11y.ts), or the code-audit-frontend agent's a11y bucket. Trigger on any axe rule id appearing in test output, not only the ones named here. Contains fix patterns for the most common violations (color-contrast, label, label-title-only, image-alt, button-name, link-name, region, landmark-one-main, heading-order, aria-allowed-attr, aria-required-attr, aria-required-children, aria-req...Votes: 0GitHub stars: 23
- Code ReviewReview code quality with adversarial rigor. Supports input modes: pending changes, PR number, commit hash, codebase scan. Always-on red-team analysis finds security holes, false assumptions, and failure modes.Votes: 0GitHub stars: 6