Code Review & Quality

Code review, refactoring, debugging, maintainability, and engineering quality

skills in category: 15,973
pages available: 666

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 browser

Browse code review & quality skills

Showing 10,753–10,776 of 15,973 skills

Code SimplifierA[Code Quality] Use when a workflow step or the user asks for code simplification: clarity, consistency, maintainability, behavior preserved.code-qualitytypescriptpythonVotes: 0GitHub stars: 3
Changes ReviewA[Code Quality] Use when a workflow step or the user asks for a review of current changes (staged/unstaged or branch diffs, focused scope). --fix-loop reviews, fixes, re-reviews. Cross-module or risky: workflow-review-changes.code-qualitytypescriptpythonVotes: 0GitHub stars: 3
Workflow Spec To PbiA[Workflow] Use when converting canonical feature/spec artifacts into prioritized, dependency-aware PBIs and stories.code-qualitygobackendVotes: 0GitHub stars: 3
Workflow Spec SyncA[Workflow] Use when updating test specs and feature docs after code changes, bug fixes, or PR reviews.code-qualitygoapiVotes: 0GitHub stars: 3
Workflow Review ChangesA[Workflow] Use when reviewing uncommitted changes that are cross-module, contract-changing or security-sensitive: specialist lenses, validated fixes, re-review until clean; --fix-loop adds an outer convergence loop. Focused diff: changes-review.code-qualityrustgoVotes: 0GitHub stars: 3
Workflow RefactorA[Workflow] Use when restructuring, reorganizing, or cleaning up code without changing behavior.code-qualitygoapiVotes: 0GitHub stars: 3
Skills DirectorySkills Directory 3 slots · $399/mo · one ad per page · sponsors can never buy grades.See placements
Workflow FeatureA[Workflow] Use when implementing a well-defined feature, component or capability (incl. TDD/test-first) where no canonical spec has the behavior yet. Spec-complete work: workflow-implement-spec.code-qualityrustgoVotes: 0GitHub stars: 3
Workflow Code To SpecA[Workflow] Use when authoring or maintaining the canonical feature/spec artifact from existing code, keeping contract, implementation and tests in sync. Idea-to-spec: workflow-idea-to-spec.code-qualitygoapiVotes: 0GitHub stars: 3
Workflow BugfixA[Workflow] Use when fixing a bug, error, or crash — root-cause investigation, fix, verification.code-qualityrustgoVotes: 0GitHub stars: 3
Why ReviewA[Code Quality] Use when a workflow step or the user asks for rationale review: why needed/chosen, trade-offs, good idea or best practice. Only explicit rationale asks; not generic reviews or how-it-works. --fix-loop fixes/re-reviews.code-qualitytypescriptpythonVotes: 0GitHub stars: 3
Web ResearchA[Research] Use when a workflow step or the user asks for web research. Gathers and triages candidate sources; `--chain=deep-dive` also deep-dives them into an evidence base.code-qualitygoVotes: 0GitHub stars: 3
TestB[Testing] Use when a workflow step or the user asks for a local test run: runs tests and analyzes the summary report.code-qualitygotestingVotes: 0GitHub stars: 3
Sync CodexA[Codex] Use when running the full Codex mirror sync and verify pipeline, or when `.claude/**` edits leave `.agents/`, `.codex/` or `AGENTS.md` stale.code-qualitypythongoVotes: 0GitHub stars: 3
Strategy BuilderA[Content] Use when a workflow step or the user asks for a marketing strategy: positioning, channels, messaging, campaigns, budget, KPIs.code-qualitygoVotes: 0GitHub stars: 3
SpecA[Documentation] Use when a workflow step or the user asks for spec authoring, auditing, amending, test-speccing, reconciling, or [mode=discovery|clarify|index]: pre-spec landscape, user-confirmed decisions, derived index/ERD.code-qualitygonodeVotes: 0GitHub stars: 3
Skill CreatorA[Skill Management] Use when creating a skill, adding skill references or scripts, fixing invalid skill headers, or packaging skills.code-qualitypythonrustVotes: 0GitHub stars: 3
ScaffoldB[Architecture] Use when a workflow step or the user asks for project scaffolding: foundations and golden-path examples before feature implementation.code-qualitygoshellVotes: 0GitHub stars: 3
Release DocA[Git] Use when creating release notes or a release document from git history at any scope (tag, branch, time range), as markdown plus a standalone HTML presentation.code-qualitygoshellVotes: 0GitHub stars: 3
Project Skill ProtocolA[Utilities] Use when a project adds, changes, lists or removes its OWN protocol rules layered over a framework skill (additive only). list | add | update | delete.code-qualitygoexpressVotes: 0GitHub stars: 3
Product RoadmapA[Planning] Use ONLY when the user explicitly requests a product roadmap, roadmap update or milestone selection: outcome milestones, MVP scope, non-goals, risks, evidence gates.code-qualitygodatabaseVotes: 0GitHub stars: 3
Llm CouncilA[Decision Support] Use when pressure-testing an irreversible, high-stakes decision with adversarial AI advisors.code-qualitypythonrustVotes: 0GitHub stars: 3
Linter SetupA[Quality] Use when a workflow step or the user asks for code quality tooling: linters, formatters, static analysis, pre-commit hooks, CI gates.code-qualityjavascripttypescriptVotes: 0GitHub stars: 3
Knowledge ReviewA[Research] Use when a workflow step or the user asks for a knowledge artifact review: completeness, citations, confidence accuracy, template compliance.code-qualitygocode-reviewVotes: 0GitHub stars: 3
Integration TestB[Testing] Use when a workflow step or the user asks for integration tests: generate them, --mode=review (one-pass 8-gate review) or --mode=verify (run with runner evidence; --fix-loop converges failures).code-qualitygobashVotes: 0GitHub stars: 3