Code Review & Quality

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

skills in category: 15,943
pages available: 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 browser

Browse code review & quality skills

Showing 12,769–12,792 of 15,943 skills

Mystenlabs Your Skill NameAReplace with a trigger-style description of when this skill should activate. Be specific — this is what the agent uses to decide whether to load the skill. Example: "Sui TypeScript SDK integration. Use when writing, reviewing, or debugging TypeScript code that interacts with Sui RPCs, transactions, or on-chain state."code-qualitytypescriptgoVotes: 0GitHub stars: 73
Mystenlabs Naming ConventionsAUse when writing or reviewing Move smart contracts on Sui. Applies to naming structs, error constants, regular constants, events, getter functions, capability types, hot potato types, and dynamic field keys. Use whenever creating new types, functions, or constants in Move code.code-qualitydebuggingdocumentationVotes: 0GitHub stars: 73
Mystenlabs MoveAMove smart contract development on Sui. Use when writing, reviewing, or debugging Move code, Move.toml configuration, or Sui object model patterns.code-qualityrusttestingVotes: 0GitHub stars: 73
Dfinity Official Reviewing MotokoADesign review for existing Motoko backends — judging whether code is well designed, not how to write it. Covers invariants encoded in types (variants over Text, correlated fields, case _ smells), stable vs transient state discipline under enhanced migration, file structure (types.mo/lib/mixins/main.mo), and severity-ranked findings (Blocker/Warning/Note). Use when reviewing, auditing, critiquing, or refactoring existing .mo files, or when asked for code-review feedback on a Motoko canister. D...code-qualitygobashVotes: 0GitHub stars: 73
Xspoonai Official Skill Pr PrepABundle pull.md and screenshot placeholders for pull request submission. Prepares all required PR documentation and assets.code-qualitypythonbashVotes: 0GitHub stars: 73
Xspoonai Official Skill Ci ChecklistAGenerate a comprehensive PR checklist for skill quality gates. Validates that skills meet submission requirements before pull request.code-qualitypythonbashVotes: 0GitHub stars: 73
Xspoonai Official Refactor Plan WriterASuggest refactor plans given a codebase summary. Analyzes code structure and proposes concrete refactoring strategies for code quality improvements.code-qualitypythonbashVotes: 0GitHub stars: 73
Xspoonai Official Github ManagerAManage GitHub issues and PRs (list, create, comment).code-qualitypythongitVotes: 0GitHub stars: 73
Xspoonai Official Github IntegrationAGitHub 集成 Skill，支持创建/查询 Issue、PR，获取仓库信息。用于 Agent 与 GitHub 协作。code-qualitypythongitVotes: 0GitHub stars: 73
Xspoonai Official Git Workflow ManagementAGit workflow automation skill for commit message generation, branch management, pre-commit checks, and change history analysiscode-qualitypythongoVotes: 0GitHub stars: 73
Xspoonai Official Code Review BasicsARun static analysis checks and emit a comprehensive code review checklist. Language-agnostic approach for reviewing code quality, style, and best practices.code-qualityjavascriptpythonVotes: 0GitHub stars: 73
Xspoonai Official Code Refactoring AdvisorAEnterprise code refactoring advisor that detects code smells, anti-patterns, and complexity issues with specific refactoring recommendations, test generation, and maintainability metricscode-qualityjavascripttypescriptVotes: 0GitHub stars: 73
Pr ReviewAFocused pull request review practices with severity-ranked, file-and-line-cited findings across four angles: security, performance, tests, and architecture. Use when asked to review a pull request, review a diff or set of changes, review \"this PR,\" or provide a code review before merge.code-qualityrustgoVotes: 0GitHub stars: 248
GitflowABranching, merging, versioning, and release conventions for the Gitflow workflow, covering main/develop branches, feature/release/hotfix branches, semantic versioning, and pull request rules. Use when creating a branch, naming a branch, planning a release or hotfix, writing a commit message, or setting up branch protection for a repository that follows Gitflow.code-qualitygogitVotes: 0GitHub stars: 248
Gamemaker GmlABest practices for GameMaker Language (GML) development, covering scripts, object events, rooms, data structures, and performance-minded game code. Use when writing GML scripts or object event code in GameMaker Studio, structuring create/step/draw events, managing rooms and instances, building state machines for gameplay, or optimizing GML for performance.code-qualitygoreactVotes: 0GitHub stars: 248
Clean CodeAClean, maintainable, human-readable code principles combined with anti-over-engineering discipline: naming, single responsibility, DRY, and scoping changes to exactly what was requested. Use when writing new code, refactoring existing code, reviewing code for quality, or deciding how much abstraction a change actually needs.code-qualitygotestingVotes: 0GitHub stars: 248
Test Like You Mean ItAUse after building any feature, model, or fix that the team has to trust — before calling it done. Replaces smoke tests and tests-written-to-pass with an adversarial test wave: tests designed to BREAK the thing (invariants, conservation laws, edge regimes, reference cross-checks, hostile inputs), where findings are expected and get fixed, not explained away. Use when the agent (or you) just wrote tests alongside the code it's testing, when a suite passes suspiciously fast, when coverage exist...code-qualityrustgoVotes: 0GitHub stars: 4
Smell The NumbersAUse whenever code produces an output someone will read — a report, a metric, a chart, a calculation result, a dashboard value — and especially when a result is surprising, suspiciously clean, or just changed a lot. Treats every implausible number as guilty until root-caused: all-zeros, -0, a value at 1858% of its physical limit, a metric that moved 40x from one run to the next, a flagship case that suddenly fails, an output that's perfectly smooth where reality is noisy. The bug is found and ...code-qualitygogitVotes: 0GitHub stars: 4
Readiness GateAUse at every 'are we ready?' moment — before declaring a task done, shipping, demoing, advancing to the next phase, or answering 'so everything works and we're good?'. Replaces vibes-based confidence ('should work now', 'looks good') with an explicit, evidence-backed go/no-go: what was verified and how, what was NOT verified, what changed, and the honest residual risk. Calibrates certainty to evidence — never asserts '100% sure' beyond what was actually tested, and never truncates the finding...code-qualityrustgoVotes: 0GitHub stars: 4
Prove Every NumberAUse whenever code contains a numeric constant, threshold, default, rate, capacity, tolerance, or coefficient — especially one the agent just introduced. Enforces the rule: every number is either derived (from real data or first principles, traceably) or cited (to a spec, datasheet, standard, or documented decision) — never invented, never tuned to make a test or demo pass. Real data is the truth; an assumption is the explicitly-labeled backup, used only when the data genuinely doesn't exist. ...code-qualityrustgoVotes: 0GitHub stars: 4
Fix It NowAUse the moment a real bug is found during any task — an audit, a review, a test wave, unrelated feature work — and the temptation appears to document it and move on. Defaults to fixing confirmed bugs in the current pass: a found bug is work surfaced, not work deferred. If a fix genuinely can't happen now (out of scope, needs a decision, blocked), the deferral must be explicit and accepted by the user — never a silent TODO buried in a report. Also fires on the half-kept feature: anything kept ...code-qualityrustgoVotes: 0GitHub stars: 4
Everywhere ElseAUse immediately after fixing a bug or improving a pattern in one place — before reporting done. Asks the question agents never ask themselves: 'did you do that anywhere else?' Enumerates the full population of sibling sites (other templates, scenarios, endpoints, components, fixtures, configs that share the same pattern), audits every one for the same defect, and applies the fix across the population — or explicitly reports which siblings were checked and found clean. Use when a fix was just ...code-qualitygodebuggingVotes: 0GitHub stars: 4
Checkpoint HandoffAUse before any context boundary — a context compaction, the end of a long session, a handoff to another agent or a future session — on multi-session work. Writes the resume state DOWN, outside the conversation: a working doc with what's done, what's in flight, the numbered remaining tasks in order, the standing constraints (the rules that must survive verbatim), and the files worth re-reading first. The test: a cold session with zero conversational memory could pick up the next task without a...code-qualitygoVotes: 0GitHub stars: 4
Bank The SuiteAUse after completing any unit of work in a repo that has a real test suite — before starting the next task, compacting context, or declaring done. Runs the FULL suite (not just the tests near the change), in the background and parallelized when it's slow, and 'banks' a green state: honest pass/fail counts, pre-existing failures explicitly carved out by name, no moving on while red is unexplained. Use when the agent only ran the two tests it just wrote, when a long suite keeps getting skipped ...code-qualityrustgoVotes: 0GitHub stars: 4