Review & quality
19,195 rows, by stacks then stars
1,766 of these skill files have been read, by 1,273 distinct authors, and what they tell an agent counted. What Review & quality authors agree on, and what they forbid
Finishing a development branch
heymegabyte/claude-skills/20-superpowers/finishing-a-development-branch Skill
no license27★ repoUse when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
heymegabyte/claude-skills/20-superpowers/receiving-code-review Skill
no license27★ repoUse 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 implementation
heymegabyte/claude-skills/20-superpowers/requesting-code-review Skill
no license27★ repoUse when completing tasks, implementing major features, or before merging to verify work meets requirements
heymegabyte/claude-skills/20-superpowers/using-git-worktrees Skill
no license27★ repoUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback
yha9806/academic-writing-toolkit/.claude/skills/evidence-review Skill
27★ repoBuild evidence-controlled literature reviews and gap maps with source-status labels, claim registers, citation-role plans, traceability tables, and overclaim audits. Use when drafting or auditing review papers, thesis literature reviews, scoping reviews, or evidence syntheses where adjacent-domain evidence, candidate records, unpublished work, and unsupported claims must be kept separate.
yha9806/academic-writing-toolkit/.claude/skills/logic-review Skill
27★ repoReview chapter drafts for paragraph-level flow, transitions, and argument continuity before editing.
yha9806/academic-writing-toolkit/.claude/skills/peer-review Skill
27★ repoReview another author's manuscript, paper, thesis chapter, proposal, or preprint as an external reviewer. Use when asked to evaluate novelty, significance, gap-contribution fit, claim-evidence adequacy, methods, evaluation, overclaim risks, structure, writing, required revisions, or recommendation without rewriting the manuscript or using private author context.
yha9806/academic-writing-toolkit/.claude/skills/self-review Skill
27★ repoReview the user's own manuscript, paper, thesis chapter, rebuttal, or release packet with clean-room anti-contamination controls. Use when asked for self-review, internal review, pre-submission review, readiness check, reviewer simulation on own work, or claim-evidence self-audit where prior chat memory, unstated assumptions, model background knowledge, or unlisted local notes must not be treated as evidence.
yha9806/academic-writing-toolkit/.claude/skills/verify-refs Skill
27★ repoUse when checking BibTeX reference records for missing fields, malformed identifiers, duplicate keys, or metadata mismatches before submission.
yha9806/academic-writing-toolkit/.claude/skills/verify Skill
27★ repoFact-check claims encountered during reading — dates, names, events, citations. Use when encountering historical facts or disputed claims.
yha9806/academic-writing-toolkit/plugins/academic-writing-toolkit/skills/argument-governance Skill
27★ repoBuild and audit the manuscript argument system: intent, gap-contribution alignment, hierarchical claims, evidence balance, limitations, and reviewer attack surfaces. Use when a paper, thesis chapter, review article, or rebuttal needs explicit intent registers, contribution chains, claim hierarchy, argument maps, evidence-fit checks, or reviewer-risk matrices before drafting, revision, peer review, or self-review.
yha9806/academic-writing-toolkit/plugins/academic-writing-toolkit/skills/evidence-review Skill
27★ repoBuild evidence-controlled literature reviews and gap maps with source-status labels, claim registers, citation-role plans, traceability tables, and overclaim audits. Use when drafting or auditing review papers, thesis literature reviews, scoping reviews, or evidence syntheses where adjacent-domain evidence, candidate records, unpublished work, and unsupported claims must be kept separate.
yha9806/academic-writing-toolkit/plugins/academic-writing-toolkit/skills/logic-review Skill
27★ repoReview chapter drafts for paragraph-level flow, transitions, and argument continuity before editing.
yha9806/academic-writing-toolkit/plugins/academic-writing-toolkit/skills/peer-review Skill
27★ repoReview another author's manuscript, paper, thesis chapter, proposal, or preprint as an external reviewer. Use when asked to evaluate novelty, significance, gap-contribution fit, claim-evidence adequacy, methods, evaluation, overclaim risks, structure, writing, required revisions, or recommendation without rewriting the manuscript or using private author context.
yha9806/academic-writing-toolkit/plugins/academic-writing-toolkit/skills/self-review Skill
27★ repoReview the user's own manuscript, paper, thesis chapter, rebuttal, or release packet with clean-room anti-contamination controls. Use when asked for self-review, internal review, pre-submission review, readiness check, reviewer simulation on own work, or claim-evidence self-audit where prior chat memory, unstated assumptions, model background knowledge, or unlisted local notes must not be treated as evidence.
yha9806/academic-writing-toolkit/plugins/academic-writing-toolkit/skills/verify-refs Skill
27★ repoUse when checking BibTeX reference records for missing fields, malformed identifiers, duplicate keys, or metadata mismatches before submission.
yha9806/academic-writing-toolkit/plugins/academic-writing-toolkit/skills/verify Skill
27★ repoFact-check claims encountered during reading — dates, names, events, citations. Use when encountering historical facts or disputed claims.
mart337i/odoo-skills/skills/odoo-code-review Skill
no license27★ repoReview Odoo addon code for correctness, security, performance, migrations, tests, and official Odoo coding guidelines. Use when reviewing Odoo modules, diffs, pull requests, or changed files involving models, fields, XML views, data, controllers, reports, OWL/assets, manifests, access rules, record rules, or OCA migrations.
The same file is in 1 other repository
mart337i/odoo-skills/skills/odoo-grill-me Skill
no license27★ repoOdoo-specific grilling session that stress-tests addon plans, migrations, model/view/security designs, OWL frontend changes, and verification strategy. Use when the user wants to be grilled on an Odoo plan/design, asks to stress-test an addon architecture, or mentions grill me in an Odoo context.
mart337i/odoo-skills/skills/odoo-idea-gates Skill
no license27★ repoOdoo-aware idea validation for deciding whether a module, addon, app, or product should exist before implementation. Use when the user wants to validate an Odoo module idea, check whether a solution already exists, assess usefulness or buyer demand, narrow a wedge, or decide whether an addon is worth building.
wonsukchoi/domain-experts/roles/biomedical-engineer Skill
27★ repoUse when a task needs the judgment of a biomedical/bioengineering engineer — running a design control phase (inputs, outputs, verification, validation) for a medical device, scoring a Design FMEA and deciding whether a failure mode needs mitigation, planning a human factors/usability validation study, building a design traceability matrix, or writing a design verification or risk-mitigation report. Distinct from a regulatory-affairs-specialist (owns the submission/clearance process, not the engineering itself) and from a clinical-data-manager/biostatistician (trial data and analysis, not device design).
Credit authorizer checker clerk
wonsukchoi/domain-experts/roles/credit-authorizer-checker-clerk Skill
27★ repoUse when a task needs the judgment of a credit authorizer, checker, or clerk — deciding a real-time point-of-sale credit authorization against available credit, verifying a credit application's income/employment documentation, issuing an adverse-action notice on a declined application, or intaking a chargeback/dispute within its filing window. Distinct from a credit analyst, who underwrites commercial credit with a multi-year financial spread and a risk rating — this role runs a high-volume rules engine against a preset limit, it does not assess creditworthiness from first principles.
wonsukchoi/domain-experts/roles/crossing-guard-flagger Skill
27★ repoUse when a task needs the judgment of a crossing guard or traffic flagger — siting a school crossing or work-zone flagger station, choosing high-visibility apparel class and taper length for a lane closure, deciding whether a crossing needs an adult guard versus a signal, or writing site-specific positioning instructions for a new location.
wonsukchoi/domain-experts/roles/physicist Skill
27★ repoUse when a task needs the judgment of a Physicist — designing an experiment to control systematic error, propagating measurement uncertainty through a derived quantity, evaluating whether a model fits data (chi-squared/goodness-of-fit), running a dimensional-analysis sanity check on a formula, or deciding whether an apparent signal is real or a statistical/systematic artifact.
wonsukchoi/domain-experts/roles/security-guard Skill
27★ repoUse when a task needs the judgment of a Security Guard — deciding whether to physically detain a suspected shoplifter or trespasser, choosing when to use force versus call police, writing a post-incident report that will hold up in a civil claim, running a fire watch or patrol schedule, or working a healthcare/retail/corporate post against written post orders.
wonsukchoi/domain-experts/roles/validation-engineer Skill
27★ repoUse when a task needs the judgment of a Validation Engineer — authoring or reviewing an IQ/OQ/PQ or process-performance-qualification (PPQ) protocol and justifying the batch/run count, computing a cleaning-validation acceptance limit (MACO from a toxicologically derived PDE/HBEL versus legacy 10 ppm or 1/1000-dose criteria), classifying a computerized system under GAMP 5 to scope CSV/CSA testing depth, auditing an existing validation package for regulatory compliance before batch release, or investigating an analytical-method validation failure against ICH Q2 acceptance criteria. Distinct from a manufacturing-engineer (owns making a process capable — fixturing, Cpk, PFMEA) — this role owns formally proving and documenting that a process, system, method, or piece of software meets its predefined requirements before it is allowed to run; the deliverable is an approved protocol or report, not a capability number.
mjunaidca/mjs-agent-skills/.claude/skills/creating-skills Skill
no license27★ repoGuides creation of effective Agent Skills with proper structure and validation. Use when users want to create a new skill, update an existing skill, or need guidance on skill design patterns, SKILL.md format, or verify.py implementation. NOT when just using existing skills (use those skills directly).
The same file is in 3 other repositories
mjunaidca/mjs-agent-skills/.claude/skills/installing-skill-tracker Skill
no license27★ repoInstalls Claude Code hooks for automatic skill usage measurement. Use when setting up skill tracking infrastructure in a new project. NOT when hooks are already installed (run verify.py to check).
Verification before completion
BlueprintOS/analysis-to-delivery/skills/orchestration/development/verification-before-completion Skill
26★ repo完成任务前验证(铁律)— 来自 superpowers 体系。本 skill 是桥接层,完整纪律见 <SUPERPOWERS_SKILL_ROOT>/verification-before-completion/。
BlueprintOS/analysis-to-delivery/skills/user-invoked/compliance-review Skill
26★ repo合规性评审 — 按 compliance-path.md 引用的合规规则,逐条评估设计。涉及 GSP / HIPAA / SOX / GDPR 等强合规场景时调用。
BlueprintOS/analysis-to-delivery/skills/user-invoked/grill-task Skill
26★ repo需求澄清 + 字段对齐分析 — 反复提问拉齐用户意图,生成 TASK_CONFIRM 任务确认书与字段对齐分析报告。启动新需求、或需要与现有数据库表对齐字段名时调用本 skill。
AlterLab-IEU/AlterLab_GameForge/skills/agents/game-qa-lead Skill
26★ repoInvoke when the user asks about testing strategy, bug tracking, playtest methodology, regression testing, release certification, QA automation, or bug triage. Triggers on: "testing", "bug", "QA", "regression", "certification", "playtest methodology", "test plan", "release gate". Do NOT invoke for usability testing (use game-ux-designer) or balance validation (use game-balance-check). Part of the AlterLab GameForge collection.
AlterLab-IEU/AlterLab_GameForge/skills/workflows/game-balance-check Skill
26★ repoInvoke when the user needs to validate game balance, tune economy systems, analyze progression curves, evaluate difficulty scaling, or check reward pacing. Includes Monte Carlo simulation and statistical validation. Triggers on: "balance", "economy tuning", "progression curve", "difficulty scaling", "reward pacing", "Monte Carlo", "fairness check". Do NOT invoke for economy/monetization design (use game-economy-designer) or code review (use game-code-review). Part of the AlterLab GameForge collection.
AlterLab-IEU/AlterLab_GameForge/skills/workflows/game-code-review Skill
26★ repoInvoke when the user wants a game-specific code review, architecture check, or technical analysis of game code. Covers frame independence, hot path performance, state machine integrity, and resource lifecycle. Triggers on: "code review", "review my code", "check architecture", "game code quality". Do NOT invoke for design document review (use game-design-review) or general sprint planning (use game-sprint-plan). Part of the AlterLab GameForge collection.
AlterLab-IEU/AlterLab_GameForge/skills/workflows/game-design-review Skill
26★ repoInvoke when the user wants feedback on a game design document, GDD review, design evaluation, or consistency check on an existing design. Triggers on: "review my GDD", "design feedback", "evaluate design", "design document review", "GDD critique". Do NOT invoke for brainstorming new ideas (use game-brainstorm) or balance tuning (use game-balance-check). Part of the AlterLab GameForge collection.
AlterLab-IEU/AlterLab_GameForge/skills/workflows/game-scope-check Skill
26★ repoEvaluate project scope against timeline and resources. Triggers on: "scope creep", "feature list", "can we fit this in", "timeline pressure", "resource constraints", "cut list", "scope evaluation". Do NOT invoke for sprint planning (use game-sprint-plan) or general project status (use game-producer). Part of the AlterLab GameForge collection.
whystrohm/shotkit/skills/visual-asset-critic Skill
26★ repoCritique a generated image against its source storyboard shot and prompt, producing revision notes. Use when the user has generated an image and wants feedback before committing. Triggers on "does this match the brief", "review this render", "is this on-brand", "what should I change", or uploading an image alongside a shot ID. The QA loop for AI visuals. Works even without a storyboard-architect run. Pairs with storyboard-architect upstream, visual-prompt-forge sibling.
api-platform/skillset/skills/api-test Skill
no license26★ repoWrites functional tests for API Platform endpoints with ApiTestCase. Use whenever the user asks to test an API resource, write or fix a functional test, verify validation, security or multi-tenant isolation, set up authentication or database fixtures for tests, or reproduce an endpoint bug with a test — including plain 'add tests for X' requests.
api-platform/skillset/skills/custom-validator Skill
no license26★ repoCreates custom validation constraints for API Platform resources. Use whenever a rule goes beyond built-in Symfony constraints — rate or plan limits, uniqueness checks, domain-specific formats, cross-field or conditional validation, or any 'reject the request when X' business rule on write operations, even if the user doesn't say 'validator'.
Workbench capy git dialogue guardrails
Fearvox/multica-ultimate-workbench/skills/workbench-capy-git-dialogue-guardrails Skill
no license26★ repoSource-first, self-loop resistant guardrails for Capy GitHub dialogue responders before any write-capable PR, issue, or review action.
Fearvox/multica-ultimate-workbench/skills/workbench-capy-process-check Skill
no license26★ repoUse when checking live Capy task or PR state through Brave, Computer Use, or a Capy browser panel.
Fearvox/multica-ultimate-workbench/skills/workbench-closeout-validator Skill
no license26★ repoStrict parser and validator for Workbench closeout comments, verdict/status discipline, PR reference types, and cross-issue REMAINING sync.
Fearvox/multica-ultimate-workbench/skills/workbench-code-review Skill
no license26★ repoFindings-first review discipline for code, diffs, task plans, live workflow changes, and implementation evidence.
Fearvox/multica-ultimate-workbench/skills/workbench-review-qa Skill
no license26★ repoPASS, FLAG, and BLOCK review discipline for workflow review, QA verification, release checks, and issue closeout.
ptsilivis/autonomousguy/skills/code-quality/code-review Skill
26★ repoSenior embedded-engineer code review. Defaults to Classic AUTOSAR embedded C and covers two concerns: (1) Correctness review — integer overflow, volatile correctness, ISR/task race conditions, stack usage, dynamic memory, control flow, AUTOSAR/ISO 26262 readiness, with findings rated Critical/Major/Minor; (2) Naming review — AUTOSAR Classic conventions for modules, SWC types, port names, runnables, C identifiers, typedefs, macros, and enumerations, aligned with MISRA Rule 5.x identifier uniqueness. Audits existing code and generates correctly-named identifiers for new work. Handles Adaptive AUTOSAR C++14+ when the input is C++ or names ara::, reviewing RAII, exceptions vs ara::core::Result, smart pointers, and AUTOSAR C++14 / MISRA C++:2023 naming. A third focus, legacy modernization assessment, proposes the smallest safe steps toward a MISRA-conformant, MCAL-abstracted, unit-tested state. Returns decision-ready findings with a built-in self-check and can emit a self-contained HTML report under analysis/.
ptsilivis/autonomousguy/skills/requirements/requirements Skill
26★ repoRequirements-engineering expert that operates in three modes: (1) Elicitation — extract atomic, testable requirements from briefs, meeting notes, or system specs using EARS notation, with full attribute set (ID, type, priority, ASIL, verification method, source), flagging ambiguities as open questions; (2) Refinement — detect requirement defects (vague qualifiers, compound statements, implementation prescription, untestability, missing attributes) and rewrite each as a specific, measurable, EARS-formatted statement with documented assumptions; (3) Traceability — build bidirectional matrices (SYS-REQ → SW-REQ → design → test), detect orphaned requirements / design elements / tests, and flag safety gaps where ASIL-tagged requirements have no test coverage (ISO 26262-6 §9 violation). Aligned with EARS, SMART, ISO 26262-6, and ASPICE SWE.1/SWE.6 practices. Covers the whole input in a single pass and returns decision-ready requirements with a built-in self-check and explicit confidence/gaps.
byerlikaya/claude-starter-kit/claude-starter/skills/code-review Skill
26★ repoCode review discipline: severity-ranked, reasoned feedback on whether a change improves the system's overall code health. review-agent-csk applies it. Trigger phrases: "code-review", "review the code", "review the PR", "review", "do a review"
byerlikaya/claude-starter-kit/claude-starter/skills/commit-message Skill
26★ repoEnterprise engineering workflow for Claude Code — not just prompts. AI agents that plan, build, audit, and ship with security gates, privacy checks, and approval-controlled commits. Safely adopt it into new or existing repositories.
byerlikaya/claude-starter-kit/claude-starter/skills/sonarqube-check Skill
26★ repoEnterprise engineering workflow for Claude Code — not just prompts. AI agents that plan, build, audit, and ship with security gates, privacy checks, and approval-controlled commits. Safely adopt it into new or existing repositories.
byerlikaya/claude-starter-kit/claude-starter/skills/trace-scan Skill
26★ repoEnterprise engineering workflow for Claude Code — not just prompts. AI agents that plan, build, audit, and ship with security gates, privacy checks, and approval-controlled commits. Safely adopt it into new or existing repositories.
byerlikaya/claude-starter-kit/plugin/skills/code-review Skill
26★ repoCode review discipline: severity-ranked, reasoned feedback on whether a change improves the system's overall code health. review-agent-csk applies it. Trigger phrases: "code-review", "review the code", "review the PR", "review", "do a review"
byerlikaya/claude-starter-kit/plugin/skills/commit-message Skill
26★ repoConventional Commits: reads the staged diff and proposes `type(scope): summary`, with body/footer when needed. One logical change = one commit. commit-agent-csk applies it. Trigger phrases: "commit message", "make a commit", "conventional commit", "write a commit", "git commit"
byerlikaya/claude-starter-kit/plugin/skills/sonarqube-check Skill
26★ repoSonarQube quality gate (language-agnostic, local-first): 0 Bugs/Vulns/Hotspots/Code Smells, 0 build warnings. If no analyzer exists, install the language's local server-less Sonar analyzer and run it — never a remote server. Trigger phrases: "sonarqube", "quality gate", "code smell", "sonar scan"
byerlikaya/claude-starter-kit/plugin/skills/trace-scan Skill
26★ repoTrace scan (§4.1/§4.2): before a commit, scans the staged changes and the message for AI traces (co-author trailers, footers, robot emoji, tool names) and vendor template names. The git hooks apply it automatically. Trigger phrases: "scan traces", "trace scan", "AI trace", "check vendor name", "pre-commit audit"
upex-galaxy/agentic-qa-boilerplate/.claude/skills/git-flow-master Skill
26★ repoEnd-to-end Git operator for any branching strategy. Auto-detects the project's strategy (solo-main, main+integration, enterprise multi-branch, trunk-based, GitFlow, GitHub Flow, GitLab Flow, SDET integration-trunk for chained test-automation suites) from .git config, branches, and the `git_strategy:` block in `.agents/project.yaml`, then adapts every commit, branch, push, PR, conflict-fix, and chained-PR action to that strategy. Use this skill whenever the user wants to: create a branch (`crear branch`, `new feature branch`, `start work on UPEX-123`), commit changes (`commit this`, `commitear esto`, `make a commit`, `commit and push`), push code (`push`, `push to main`, `push to staging`, `subir cambios`), open a pull request (`create PR`, `open PR`, `abrir PR`, `crear pull request`, `gh pr create`), fix merge conflicts (`fix conflict`, `resolver conflicto`, `merge conflict`, `rebase conflict`, `push rejected`), plan stacked or chained PRs (`stack of PRs`, `chained PRs`, `split this PR`, `PR demasiado grande`), set up an isolated git worktree (`worktree`, `work in a worktree`, `isolate this work`, `parallel session`, `aislar el trabajo`, `trabajar aislado`), set up or bootstrap a branching strategy on a fresh repo (`set up our git strategy`, `bootstrap branching`, `configura el flujo de git`, `git strategy setup`, `materialize the git flow`, `create the staging branch and write the runbook`), or pick / change / set up a branching strategy (`git flow`, `git strategy`, `branching strategy`, `which git flow do we use`, `set up our git strategy`, `bootstrap branching`, `configura el flujo de git`). Trigger even when the user does not say `git-flow-master` literally — if the work is git-or-PR-shaped, this is the right tool. Do NOT use for: testing tickets (use /sprint-testing), authoring test cases in TMS (use /test-documentation), writing automated tests (use /test-automation), running regression suites (use /regression-testing), or general code editing — git-flow-master operates strictly on the version-control layer.
Dataslayer-AI/Marketing-skills/skills/ds-eval Skill
26★ repoInternal development tool that tests whether skill descriptions trigger correctly for different user inputs. Reads test cases from a YAML file and evaluates each one by matching the input against all skill descriptions. Use when the user says "run triggering eval", "test skill descriptions", "check triggering accuracy", "eval skills", or after editing a skill description to verify it still triggers correctly.
Dataslayer-AI/Marketing-skills/skills/ds-lint Skill
26★ repoInternal development tool that validates all SKILL.md and agent .md files against the Claude Code spec. Checks frontmatter completeness, field validity, allowed-tools presence, line count, hardcoded paths, and description quality. Use when the user says "lint skills", "validate skills", "check skill quality", "run the linter", "are my skills valid", or before shipping changes to the skills repo.
stablyai/agent-skills/skills/stably-verify Skill
no license26★ repoVerify that an application works correctly using `stably verify`. Use when an AI agent has made code changes and needs to validate the feature works in a real browser. The command describes expected behavior in plain English and reports a PASS/FAIL/INCONCLUSIVE verdict — no test files generated. Triggers on: "verify this works", "stably verify", "check if this works", "validate my changes", "verify my feature", "does this work", "check the app", "verify the feature".
hankunpeng/skills/skills/conventional-commits Skill
26★ repoEnforce, validate, lint, and manage Conventional Commits across git repositories. Generates semantic changelogs and installs git hooks. Use this skill whenever the user mentions commit messages, commit conventions, conventional commits, semantic versioning, changelogs, commit linting, git hooks for commits, or wants to standardize their commit format — even if they don't explicitly say "conventional commits".
oribarilan/97/skills/self-review Skill
no license25★ repoUse when about to commit, finish a task, open a PR, summarize work for the user, or when the user asks for a review or summary — NOT just on autonomous commits, which are rare in OpenCode usage