All categories
Code Review & Quality
Code review, refactoring, debugging, maintainability, and engineering quality
- 15,941
- 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 1,801–1,824 of 15,941 skills
- Repo ScanCross-stack source code asset audit — classifies every file, detects embedded third-party libraries, and delivers actionable four-level verdicts per module with interactive HTML reports.Votes: 0GitHub stars: 17
- Project Flow OpsOperate execution flow across GitHub and Linear by triaging issues and pull requests, linking active work, and keeping GitHub public-facing while Linear remains the internal execution layer. Use when the user wants backlog control, PR triage, or GitHub-to-Linear coordination.Votes: 0GitHub stars: 17
- Debug Checklist**Version**: 1.0.0 **Author**: Claw **License**: MIT ---Votes: 0GitHub stars: 12
- Compound DocsDocument solved problems for team reuse. Provides process knowledge for /ia-compound. Use when documenting a resolved issue, writing up lessons learned, capturing a post-mortem, adding to the knowledge base, or building searchable institutional knowledge after debugging.Votes: 0GitHub stars: 12
- Using Agent SkillsDiscovers and invokes agent skills. Use when starting a session or when you need to discover which skill applies to the current task. This is the meta-skill that governs how all other skills are discovered and invoked.Votes: 0GitHub stars: 12
- Idea RefineRefines ideas iteratively. Refine ideas through structured divergent and convergent thinking. Use "idea-refine" or "ideate" to trigger.Votes: 0GitHub stars: 12
- Command GuideClaude Code Command Selection Guide - Automatically recommend and select the right commands, agents, and skills in Claude Code. Use when: (1) user is unsure which command or tool to use, (2) needs to decide which agent/skill best fits the current task, (3) querying usage scenarios for /plan, /tdd, /compact, /loop and other commands, (4) understanding when to invoke planner, code-reviewer, build-error-resolver and other agents, (5) needs command cheat sheet or decision flowchart. Triggers: "wh...Votes: 0GitHub stars: 12
- Karpathy CoderUse when writing, reviewing, or committing code to enforce Karpathy's 4 coding principles — surface assumptions before coding, keep it simple, make surgical changes, define verifiable goals. Triggers on "review my diff", "check complexity", "am I overcomplicating this", "karpathy check", "before I commit", or any code quality concern where the LLM might be overcoding.Votes: 0GitHub stars: 12
- Swiftui Expert SkillWrite, review, or improve SwiftUI code following best practices for state management, view composition, performance, modern APIs, Swift concurrency, and iOS 26+ Liquid Glass adoption. Use when building new SwiftUI features, refactoring existing views, reviewing code quality, or adopting modern SwiftUI patterns.Votes: 0GitHub stars: 12
- Review SwarmAdversarial code review of a diff or pull request by seven independent reviewer subagents with distinct mandates (security and secrets handling; correctness and concurrency; data loss, migration and backward compatibility; documentation-vs-reality truthfulness; regressions against the project's git and pull-request history; the project's own written rules in AGENTS.md/CLAUDE.md and directive comments; performance), each forbidden from reporting anything it cannot quote verbatim from the code,...Votes: 0GitHub stars: 2
- Project PlanPlan project work by creating or updating a detailed design document (approved by the user before planning), then deriving an implementation plan with cohesive, session-sized milestones and mandatory testing and review gates, then executing one milestone per session with recorded evidence and a handoff. Use for "plan this project", "design doc", "turn this design into an implementation plan", "break this work into milestones", or "what's next on this project"; also use when the project alread...Votes: 0GitHub stars: 2
- Sdd ReviewIndependent, traceable code review of one SDD Composy task in review_required against its approved PRD, stories, TechSpec, evidence, and project rules, with stable findings and severities. Use when a task passed QA and evidence — 'revisar a TASK-003', 'code review da task', 'review this task's diff'. Do NOT use for code review outside an SDD workspace (use the host code review), for QA (sdd-qa), or for verification (sdd-verify).Votes: 0GitHub stars: 3
- Sdd MapProduce a deterministic, read-only evidence map of the repository for SDD Composy (languages, manifests, commands, modules, boundaries, staleness) and publish the context bundle only on request. Use before a PRD or TechSpec, or when the map is stale — 'mapear o repositório', 'atualizar o contexto do código', 'what does this codebase look like for SDD'. Do NOT use for architecture decisions, code review, or repository exploration without an SDD workspace.Votes: 0GitHub stars: 3
- Skill RefactorReview or refactor an existing SKILL.md and its bundled resources — a smaller always-loaded core, conditional references, preserved behavior, lean/guided consumer profiles, and an A/B protocol to compare a candidate with the previous version. Use when a skill repeats itself, loads references on every run, triggers too broadly or misses legitimate requests, or needs its efficiency measured across models. Do NOT use for writing a new skill from scratch, refactoring application code, translating...Votes: 0GitHub stars: 3
- ForgemasterRoute a task by complexity and run the gated Forge pipeline (research → plan → implement → ship). Use when the user runs /forgemaster or wants the full guided feature pipeline.Votes: 0GitHub stars: 2
- Forgemaster AutoRun the full Forge pipeline unattended: each phase is reviewed by a fresh evaluator subagent, the findings feed back, and the run advances itself. Use when the user runs /forgemaster-auto or wants a feature built end to end without approval gates.Votes: 0GitHub stars: 2
- Writing SkillsUse when creating new skills, editing existing skills, or verifying skills work before deploymentVotes: 0GitHub stars: 8
- Nestjs Best PracticesNestJS best practices and architecture patterns for building production-ready applications. This skill should be used when writing, reviewing, or refactoring NestJS code to ensure proper patterns for modules, dependency injection, security, and performance.Votes: 0GitHub stars: 8
- Clean Room RedesignPlans and oversees a clean-room rewrite from existing behavior. Use for greenfield redesigns and aggressive legacy replacements.Votes: 0GitHub stars: 38
- Metamask Official Sentry QuotaCatch quota-risky Sentry span instrumentation in code and PRs — fan-out × ungated × no-kill-switch — before it blows the span budgetVotes: 0GitHub stars: 76
- Metamask Official Selector Antipattern ScanReview and diagnose Redux selector antipatterns that cause render cascades, pre-merge and post-mergeVotes: 0GitHub stars: 76
- Metamask Official Decompose Large FilesDecompose a large file into coherent, independently-mergeable modules to improve modularity, maintainability, reviewability, and code organization — and to unblock incremental TS migration. Extract by coherent subject/domain cluster; never fragment for its own sake.Votes: 0GitHub stars: 76
- Danthamanvoiss Skill Boundary AuditCheck nearby skills for overlap, ambiguity, or confused ownership so the suite stays easy to route.Votes: 0GitHub stars: 76
- Danthamanvoiss Routing Confidence CheckSanity-check whether the selected router path and skill stack are the clearest minimal fit for the task.Votes: 0GitHub stars: 76