All categories
Code Review & Quality
Code review, refactoring, debugging, maintainability, and engineering quality
- 16,449
- 686
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 9,457–9,480 of 16,449 skills
- GitnexusUnified GitNexus dispatcher for CLI, guide, exploration, debugging, PR review, impact analysis, and refactoring workflows. Use when the user says 'run gitnexus', 'analyze this repo', 'check impact', 'trace dependencies', or 'review this PR'.Votes: 0GitHub stars: 2
- Gitnexus GuideUse when the user asks about GitNexus itself — available tools, how to query the knowledge graph, MCP resources, graph schema, or workflow reference. Examples: \"What GitNexus tools are available?\", \"How do I use GitNexus?\"Votes: 0GitHub stars: 2
- Yuri Code IntelligenceUnified code quality intelligence layer that diagnoses code smells (Long Method, Feature Envy, design pattern issues), prescribes targeted Fowler refactoring techniques, and reviews code for security, performance, and clarity. Use when user says 'review this code', 'refactor this', 'what's wrong with this method', 'code smells', or 'clean this up'.Votes: 0GitHub stars: 2
- Writing SkillsUse when creating new skills, editing existing skills, or verifying skills work before deploymentVotes: 0GitHub stars: 2
- Visual IntrospectionEngineering visual analysis of the Yuri OS architecture graph. Reads _SYSTEM/yuri-graph-state.json and reports structural insights, optimization opportunities, dead-ends, missing returns, duplicate functionality, and merge candidates. Use when reviewing system architecture, planning refactors, or assessing graph health.Votes: 0GitHub stars: 2
- Systematic DebuggingUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesVotes: 0GitHub stars: 2
- Subagent Driven DevelopmentUse when executing implementation plans with independent tasks in the current sessionVotes: 0GitHub stars: 2
- SharinganUser-invoked reverse-engineering + enhancement protocol for any source artifact: repos, codebases, docs, PDFs, screenshots, specs, workflows. Observe deeply, extract underlying technique (not property), expose weaknesses, then rebuild as a legally clean, Yuri OS / Yuri-aligned diamond design via 9-phase pipeline. Use when the user says \"activate Sharingan\", \"reverse-engineer this\", \"copy the technique not the code\", or wants to deeply understand and rebuild an artifact from first princi...Votes: 0GitHub stars: 2
- Requesting Code ReviewUse when completing tasks, implementing major features, or before merging to verify work meets requirementsVotes: 0GitHub stars: 2
- Improve Codebase ArchitectureFind deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.Votes: 0GitHub stars: 2
- GitnexusUnified GitNexus dispatcher for CLI, guide, exploration, debugging, PR review, impact analysis, and refactoring workflows. Use when the user says 'run gitnexus', 'analyze this repo', 'check impact', 'trace dependencies', or 'review this PR'.Votes: 0GitHub stars: 2
- Gitnexus Pr ReviewUse when the user wants to review a pull request, understand what a PR changes, assess risk of merging, or check for missing test coverage. Examples: \"Review this PR\", \"What does PR #42 change?\", \"Is this PR safe to merge?\"Votes: 0GitHub stars: 2
- Gitnexus GuideUse when the user asks about GitNexus itself — available tools, how to query the knowledge graph, MCP resources, graph schema, or workflow reference. Examples: \"What GitNexus tools are available?\", \"How do I use GitNexus?\"Votes: 0GitHub stars: 2
- Dispatching Parallel AgentsUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesVotes: 0GitHub stars: 2
- BrainstormingYou MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.Votes: 0GitHub stars: 2
- Yuri Shura6-perspective adversarial review for high-stakes turns (architecture decisions, refactor planning, deployment review) — fans out architect, adversary (7-vector attack), maintainer, ops, product, and security perspectives in parallel, then consolidates. Use when user says 'review this decision', '/shura', 'adversarial review', 'what could go wrong', 'architecture review', or 'deployment review'.Votes: 0GitHub stars: 2
- Yuri Code IntelligenceUnified code quality intelligence layer that diagnoses code smells (Long Method, Feature Envy, design pattern issues), prescribes targeted Fowler refactoring techniques, and reviews code for security, performance, and clarity. Use when user says 'review this code', 'refactor this', 'what's wrong with this method', 'code smells', or 'clean this up'.Votes: 0GitHub stars: 2
- Visual IntrospectionEngineering visual analysis of the Yuri OS architecture graph. Reads _SYSTEM/yuri-graph-state.json and reports structural insights, optimization opportunities, dead-ends, missing returns, duplicate functionality, and merge candidates. Use when reviewing system architecture, planning refactors, or assessing graph health.Votes: 0GitHub stars: 2
- Systematic DebuggingUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesVotes: 0GitHub stars: 2
- Setup Matt Pocock SkillsScaffolds per-repo configuration (issue tracker, triage labels, domain doc layout) that engineering skills assume. Use when first running `to-issues`, `to-prd`, `triage`, `diagnose`, `tdd`, `improve-codebase-architecture`, or `zoom-out` in a new repo, or when those skills appear to be missing context about the issue tracker, triage labels, or domain docs.Votes: 0GitHub stars: 2
- Requesting Code ReviewUse when completing tasks, implementing major features, or before merging to verify work meets requirementsVotes: 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: 2
- Izanagi SimulatorCounterfactual simulation engine that generates 3 divergent alternate paths before committing to high-stakes plans, evaluating each by EV/risk/reversibility with explicit simulation records. Use when facing CRITICAL or HIGH complexity decisions with multiple viable paths, when the user says \"simulate this decision\", \"what if we tried X instead\", or \"I need to evaluate alternatives before committing\".Votes: 0GitHub stars: 2
- Improve Codebase ArchitectureFind deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.Votes: 0GitHub stars: 2