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
PramodDutta/qaskills/seed-skills/ssl-tls-testing Skill
201★ repoSSL/TLS configuration testing including certificate validation, cipher suite analysis, protocol version checks, and HSTS verification.
PramodDutta/qaskills/seed-skills/static-analysis-custom-rules Skill
201★ repoWriting custom static analysis rules for ESLint, Semgrep, and SonarQube to enforce project-specific code quality and security standards.
Verification before completion
PramodDutta/qaskills/seed-skills/verification-before-completion Skill
201★ repoEnforces rigorous verification evidence before any claims of task completion, preventing false positives, untested deployments, and premature celebration with a structured gate function.
PramodDutta/qaskills/seed-skills/vibe-check Skill
201★ repoBrowser automation for AI agents. Navigate pages, fill forms, click elements, take screenshots, and manage tabs — all through simple CLI commands. 2.6k+ GitHub stars.
PramodDutta/qaskills/seed-skills/webhook-testing Skill
201★ repoTesting webhook implementations including delivery verification, retry logic, signature validation, idempotency, and failure handling patterns.
PramodDutta/qaskills/seed-skills/zod-schema-testing Skill
201★ repoComprehensive testing patterns for Zod schemas covering validation testing, transform testing, error message verification, and integration with API endpoints and forms
hiyeshu/codeck/skills/codeck-review Skill
199★ repoReviewer role. Opens rendered HTML, inspects every slide visually, fixes problems in custom.css or slides.html and rebuilds through build-html.sh. Use whenever the user says "review", "QA", "check slides", "inspect", "audit", "proofread", or wants feedback on a rendered deck.
vishalsachdev/canvas-mcp/skills/canvas-morning-check Skill
199★ repoEducator morning course health check for Canvas LMS. Shows submission rates, struggling students, grade distribution, and upcoming deadlines. Trigger phrases include "morning check", "course status", "how are my students", or any start-of-day teaching review.
The same file is in 4 other repositories
vishalsachdev/canvas-mcp/skills/canvas-peer-review-manager Skill
199★ repoEducator peer review management for Canvas LMS. Tracks completion rates, analyzes comment quality, flags problematic reviews, sends targeted reminders, and generates instructor-ready reports. Trigger phrases include "peer review status", "how are peer reviews going", "who hasn't reviewed", "review quality", or any peer review follow-up task.
The same file is in 4 other repositories
stevenflanagan1/social-ai-team/skills/social-performance-review Skill
no license196★ repoMonthly social media performance review for SMBs. Analyses post-level and account-level data from Instagram, LinkedIn, Facebook, or TikTok. Identifies what worked, what didn't, and why. Produces a client-ready report and specific recommendations that feed back into the content calendar. Accepts CSV exports, screenshots, or manual data input.
The same file is in 2 other repositories
cxuu/golang-skills/skills/go-linting Skill
195★ repoUse when setting up linting for a Go project, configuring golangci-lint, or adding Go checks to a CI/CD pipeline. Also use when starting a new Go project and deciding which linters to enable, even if the user only asks about "code quality" or "static analysis" without mentioning specific linter names. Does not cover code review process (see go-code-review).
The same file is in 3 other repositories
gaasher/Agent-Loop-Skills/loops/claim-verify Skill
183★ repoUse when the user has a results draft or a set of data-backed claims and wants each one adversarially verified against the underlying dataset before publishing — a pre-publication red-team of the findings. Extracts the discrete checkable claims from the draft, reproduces each claim's number against the data, stress-tests it against the threats most likely to kill it (outliers, confounds, Simpson's reversals, tiny subgroups, alternative specifications), and marks it verified, fragile, or refuted; fragile and refuted claims are revised — hedged, scoped, or retracted — until every claim is verified or appropriately qualified. The result is a draft where every surviving claim has been reproduced and survived a stress test. Not for open-ended discovery of new findings over a dataset (that is a data-analysis task), and not for diagnosing a single known anomaly or pipeline failure — this is a gate over an existing draft.
gaasher/Agent-Loop-Skills/loops/karpathy Skill
183★ repoUse when the user wants the LLM to do its own ML research: a fully-autonomous loop that hacks the training code, runs it, and keeps changes that lower a single scalar metric (e.g. val_bpb). One agent proposes one change at a time, runs training in the user's env, keeps it only if the metric improves (advancing a git branch) else reverts, and loops forever until the human interrupts. A faithful adaptation of Karpathy's autoresearch. Not for the analysis-first variant that profiles before editing (that is ml-autoresearch), and not for a budgeted, plateau-stopping refactor.
gaasher/Agent-Loop-Skills/loops/scientific-writer Skill
183★ repoUse when the user has a scientific draft (with its dataset, figures, and optional analysis code) and wants it iteratively revised until it clears a quality bar. Five specialist judges (figures, scientific content, style, formatting, code) critique the draft; a fresh, independent peer_reviewer grades it on those same axes (1-5 each → a percentage) with honesty guardrails; a scientific_writer revises prose, figures, and code — regenerating figures by running the user's plot command — until the peer-review score clears the threshold or the budget is hit. Not for writing a paper from a blank page, and not for a standalone literature survey.
wanshuiyin/Anti-Autoresearch/skills/citation-forensics Skill
180★ repoCitation-integrity forensics: is every reference real, correctly attributed, and used in a context the cited work actually supports? Catches hallucinated references (no paper at the claimed arXiv id/DOI/venue, fabricated authors/year), metadata drift (wrong year/venue/version), and wrong-context citations (a real paper cited for a claim it never makes — or argues against). A hot zone for machine-generated papers. Decidable at L0 (text + canonical sources). Span-anchored to the evidence ledger (claims.json); the executor gathers canonical facts (DBLP / arXiv / DOI), then one FRESH cross-model thread per cited key proposes findings; reviewer != adjudicator. Emits citation-forensics.findings.json; NEVER computes the verdict. Triggers: "citation forensics", "check the references", "hallucinated citations", "wrong-context citation", "verify references", "引用核对".
wanshuiyin/Anti-Autoresearch/skills/experiment-forensics Skill
180★ repoAudit experiment integrity against the evidence ledger. At L2 (repo + result files present) a fresh cross-model reviewer reads the eval code line-by-line for fake/derived ground truth, score self-normalization, phantom results (a paper number with no backing file/key), dead/uncalled metric code, verified-scope inflation, method-described ≠ method-evaluated drift, synthesized-looking results, placeholder/fake data still wired into a released result, code-output ≠ reported-number mismatch, and missing reproducibility artifacts (an empirical/agent/LLM paper shipping neither code nor the prompts/configs its results need) — every finding span-anchored to a ledger claim_id. At L0/L1 (PDF / source only) the same patterns are surfaced as info-level 'could-not-verify' signals where the ledger gives an anchor (observability_level_required:2) — NEVER a fraud verdict from a PDF. The reviewer PROPOSES findings; tools/adjudicate_findings.py computes the verdict. Detect-only. Triggers: "experiment forensics", "audit the results", "check the eval code", "实验诚实度".
wanshuiyin/Anti-Autoresearch/workflows/anti-autoresearch Skill
180★ repoEnd-to-end substantive-integrity forensic sweep of a research paper (especially autoresearch / AI-Scientist-style output). Orchestrates the whole pipeline: ingest (arxiv-id | pdf | dir → working dir + pdftotext for L0) → /evidence-ledger (artifact manifest + observability level L0/L1/L2 + span-anchored claims.json) → fan out the integrity auditor skills (consistency, citation, baseline, experiment, presentation, proof-derivation, eval-design — each reads the ledger, emits span-anchored findings) + the zero-verdict-weight AIS writing-style track → advisory memos (/adversarial-case-builder + /novelty-duplication-advisory, no verdict weight) → deterministic tools/adjudicate_findings.py (--ledger REQUIRED) → reviewer-ready Integrity Forensics Report. Cross-model (fresh codex per dimension) and reviewer≠adjudicator: the model proposes findings, the deterministic adjudicator decides the verdict. Observability-aware, detect-only, never an opaque AI-text classifier (a separate zero-weight AIS section lists AI writing-style impressions, never moving the verdict). Triggers: "anti-autoresearch", "integrity audit this paper", "forensic review", "audit a submission", "审一篇投稿的诚信".
techygarg/lattice/skills/atoms/secure-coding Skill
179★ repoApply security-conscious thinking when generating or modifying code. Enforces trust boundary awareness, input validation, injection prevention, secrets management, and defense-in-depth authorization. Use when generating code that handles user input, authentication, authorization, database queries, external APIs, file operations, or when the user mentions 'security review', 'secure this', 'check for vulnerabilities', 'trust boundary', 'input validation', or 'OWASP'. This skill governs the security posture of generated code -- not architecture (see architecture) and not code craft (see clean-code).
The same file is in 1 other repository
techygarg/lattice/skills/molecules/review Skill
179★ repoPerform a structured code review by composing validation checklists from relevant atoms based on what code changed. Loads atoms conditionally -- clean-code always, architecture/DDD/security/tests only when the delta touches their domain. Produces a severity-ordered report with specific locations and fixes. Use when the user asks to 'review this', 'code review', 'quality check', 'validate the code', 'check my code', 'review the delta', or 'review this PR'.
The same file is in 1 other repository
techygarg/lattice/skills/refiners/review-refiner Skill
179★ repoFacilitate a structured conversation to customize how the review molecule works -- atom loading rules, severity classification, report format, scope rules, insight capture, and health logging. Produces a formal review-standards.md document that the review molecule will use as its process configuration. Use when the user says 'customize review', 'configure review', 'review preferences', 'review settings', 'change review process', or 'set up review'.
The same file is in 1 other repository
techygarg/lattice/dev-skills/skill-review Skill
176★ repoDeep behavioral audit of a Lattice skill — proposes 3 review personas relevant to the skill, runs independent scenario analysis from each persona's perspective, then merges only the high-confidence, practical findings into a severity-ordered gap report with proposed fixes. Structural validation (conventions, cross-references) is skill-validate's job — this skill finds gaps that would realistically surface when someone actually uses the skill: missing scenario handling, ambiguous instructions, silent failure cases, and behavioral inconsistencies. Filters out theoretical edge cases, low-likelihood speculation, and findings owned by other skills. Use after writing or significantly changing any skill, or when the user says 'review this skill', 'deep review', 'does this skill work', 'find gaps in this skill', 'stress test this skill', 'review from different angles', or 'skill review'. Standalone — does not call other skills.
techygarg/lattice/plugins/lattice/skills/review-refiner Skill
176★ repoFacilitate a structured conversation to customize how the review molecule works -- atom loading rules, severity classification, report format, scope rules, insight capture, and health logging. Produces a formal review-standards.md document that the review molecule will use as its process configuration. Use when the user says 'customize review', 'configure review', 'review preferences', 'review settings', 'change review process', or 'set up review'.
techygarg/lattice/plugins/lattice/skills/review Skill
176★ repoPerform a structured code review by composing validation checklists from relevant atoms based on what code changed. Loads atoms conditionally -- clean-code always, architecture/DDD/security/tests only when the delta touches their domain. Produces a severity-ordered report with specific locations and fixes. Use when the user asks to 'review this', 'code review', 'quality check', 'validate the code', 'check my code', 'review the delta', or 'review this PR'.
techygarg/lattice/plugins/lattice/skills/secure-coding Skill
176★ repoApply security-conscious thinking when generating or modifying code. Enforces trust boundary awareness, input validation, injection prevention, secrets management, and defense-in-depth authorization. Use when generating code that handles user input, authentication, authorization, database queries, external APIs, file operations, or when the user mentions 'security review', 'secure this', 'check for vulnerabilities', 'trust boundary', 'input validation', or 'OWASP'. This skill governs the security posture of generated code -- not architecture (see architecture) and not code craft (see clean-code).
wednesday-solutions/ai-agent-skills/skills/agents/pr-review-agent Skill
174★ repoFull PR review orchestrator. Use when asked to review a PR or check if it is ready to merge. Runs blast radius + drift check on changed files, then hands off to pr-review for comment triage and fixes. Do NOT use pr-review directly for full reviews — use this.
wednesday-solutions/ai-agent-skills/skills/pr-review Skill
174★ repoFix engine for PR review comments. Fetches review comments (Gemini bot or human), categorizes by impact, posts a prioritized fix queue, and applies fixes on dev approval. Called directly for quick fixes, or internally by pr-review-agent as part of full PR review.
The same file is in 1 other repository
wednesday-solutions/ai-agent-skills/skills/wednesday-git Skill
174★ repoUnified Git workflow. Manages the entire task lifecycle: branch creation (sprint), atomic commits (git-os), and PR opening (pr-create).
The same file is in 1 other repository
magnus919/agent-skills/bundles/neckbeard Skill
169★ repoUse when asked to fix, build, refactor, review, verify, or release software and the work is non-trivial. neckbeard routes the change through framing, discovery, design, implementation, review, verification, delivery, and learning — choosing the smallest *safe* intervention, proving it at the real delivery boundary, and leaving an inspectable evidence ledger. Composes specialist catalog skills rather than replacing them. Not a persona, not a '10x developer' prompt, not a LOC-minimizer.
magnus919/agent-skills/flaresolverr Skill
169★ repoUse the minimal FlareSolverr wrapper for a one-off health check or browser-backed GET/POST when ordinary retrieval is blocked by Cloudflare or DDoS-GUARD. Choose flaresolverr-cli instead for named session lifecycle, cookie-only returns, dry-run planning, or the full operational command surface.
magnus919/agent-skills/spec-driven-development Skill
169★ repoSpec-Driven Development (SDD) methodology for AI software factories — where structured specifications are the input, AI agents generate the code, and quality gates enforce correctness at each pipeline phase. Use when designing a spec → review → decompose → implement → verify pipeline that any AI coding tool (Claude Code, Cursor, Hermes Agent, Devin, OpenHands) can follow.
magnus919/agent-skills/verification-methodology Skill
169★ repoVerify work against explicit criteria using direct, source-faithful evidence, reproducible checks, and clear verdicts. Use before declaring an artifact, implementation, or claim complete; do not use for exploratory research without pass/fail criteria.
Impertio-Studio/Frappe_Claude_Skill_Package/skills/source/agents/frappe-agent-validator Skill
no license167★ repoUse when reviewing or validating Frappe/ERPNext code against best practices and common pitfalls. Checks generated code before deployment, validates against all 61 frappe-* skills, catches v16 patterns (extend_doctype_class, type annotations), validates ops patterns (bench commands, deployment), and generates correction reports. Keywords: review code, check script, validate deployment, find bugs, code quality, check my code, is this correct, code review, before deploying, best practices check.
Impertio-Studio/Frappe_Claude_Skill_Package/skills/source/testing/frappe-testing-cicd Skill
no license167★ repoUse when setting up CI/CD pipelines for Frappe apps, configuring GitHub Actions test workflows, or adding linting and security scanning. Prevents broken CI from incorrect test matrix configuration, missing MariaDB/Redis services, and uncaught code quality issues. Covers GitHub Actions workflows, test matrix (Python/Node versions), semgrep rules, pre-commit hooks, linting (ruff, eslint), CI test environment setup. Keywords: CI/CD, GitHub Actions, test matrix, semgrep, pre-commit, linting, ruff, eslint, continuous integration, automated tests, GitHub Actions, CI pipeline, pre-commit, code quality check..
TabooHarmony/roblox-brain/skills/roblox-code-review Skill
166★ repoGive your AI coding agent a Roblox brain. Curated skills for Roblox Studio development.
kairyou/agent-tools/skills/workflow/at-commit Skill
166★ repoGenerate a Conventional Commits message from staged changes and wait for confirmation before committing. Use when the user asks to commit or generate a commit message.
kairyou/agent-tools/skills/workflow/at-review Skill
166★ repoReview code changes for bugs, regressions, convention violations, and high-value cleanup opportunities. Use for diffs, commit ranges, PRs, paths, staged changes, or working-tree changes.
QinghongLin/data2story-skill/skills/data2story-pro/inspector Skill
152★ repoRun sentence-level traceability verification on a Data2Story blog (verify.py -> verifier.json), then emit the in-page Inspector panel (the reader-facing runnable verifier) + the verify/ artifacts (verify_map.json, run_cells.json, the reproducible notebook, cell_registry.json). Mostly Python; the runnable layer recomputes each computation in-browser from its inlined data and grades it against the published output, while the bundled notebook re-executes from raw data. Use verify.py at Stage 6.4 (after validate.py, before the Critic) and generate_viewer.py at Stage 7 after the Programmer authors the verify/ files and pastes the panel shell. Triggers: a built index.html plus the role JSONs exist, or you need the traceability map / the in-page runnable verifier.
QinghongLin/data2story-skill/skills/sparring-partner Skill
152★ repoThis skill should be used whenever the user wants to develop, refine, or stress-test an idea, plan, design, research direction, product/business concept, argument, or any decision with more than one reasonable path — i.e. whenever they want a thinking partner rather than a quick answer. Trigger it when the user says things like "let's brainstorm", "help me think through this", "poke holes in my idea", "be my devil's advocate", "roast this idea", "challenge my assumptions", "sanity-check my plan", "what am I missing?", "I have a rough idea for…", or shares a half-baked concept and wants to make it better — even if they never use the word "brainstorm". It makes Claude a rigorous, anti-sycophantic sparring partner that researches just-in-time, drives the idea through Frame → Diverge → Converge → Pressure-test → Decide, asks sharp questions, and refuses to rubber-stamp. Do NOT use it for simple factual lookups, well-defined tasks with one correct answer, or when the user just wants direct execution of a clear instruction.
w95/awesome-claude-corporate-skills/02-finance-accounting/check-model Skill
150★ repo166 production-ready Claude AI skills organized by corporate role — executive leadership, finance, HR, marketing, sales, legal, operations, engineering, product, data, customer success, procurement & document processing
w95/awesome-claude-corporate-skills/02-finance-accounting/client-review Skill
150★ repo166 production-ready Claude AI skills organized by corporate role — executive leadership, finance, HR, marketing, sales, legal, operations, engineering, product, data, customer success, procurement & document processing
The same file is in 1 other repository
w95/awesome-claude-corporate-skills/03-human-resources/performance-review-assistant Skill
150★ repoTRIGGER THIS when conducting performance reviews, writing manager feedback, creating self-assessments, building peer feedback, developing PIPs, creating development plans, or handling difficult performance conversations. Helps write constructive, specific, actionable feedback that develops performance and documents performance management appropriately.
w95/awesome-claude-corporate-skills/06-legal-compliance/contract-review Skill
150★ repoReview contracts against your organization's negotiation playbook, flagging deviations and generating redline suggestions. Use when reviewing vendor contracts, customer agreements, or any commercial agreement where you need clause-by-clause analysis against standard positions.
w95/awesome-claude-corporate-skills/08-it-engineering/changelog-generator Skill
150★ repoAutomatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
The same file is in 14 other repositories
w95/awesome-claude-corporate-skills/08-it-engineering/code-review Skill
150★ repoReview code for bugs, security vulnerabilities, performance issues, and maintainability. Trigger with "review this code", "check this PR", "look at this diff", "is this code safe?", or when the user shares code and asks for feedback.
w95/awesome-claude-corporate-skills/10-data-analytics/data-validation Skill
150★ repoQA an analysis before sharing with stakeholders — methodology checks, accuracy verification, and bias detection. Use when reviewing an analysis for errors, checking for survivorship bias, validating aggregation logic, or preparing documentation for reproducibility.
The same file is in 1 other repository
serpro69/claude-toolbox/klaude-plugin/skills/chain-of-verification Skill
no license147★ repoApply Chain-of-Verification (CoVe) prompting to improve response accuracy through self-verification. Use when complex questions require fact-checking, technical accuracy, or multi-step reasoning.
serpro69/claude-toolbox/klaude-plugin/skills/diff-skill/evals/clean-refactor/test-files/after Skill
no license147★ repoReviews tool configurations for correctness.
serpro69/claude-toolbox/klaude-plugin/skills/diff-skill/evals/clean-refactor/test-files/before Skill
no license147★ repoReviews tool configurations for correctness.
serpro69/claude-toolbox/klaude-plugin/skills/review-code Skill
no license147★ repoCode review of current git changes with an expert senior-engineer lens. Detects SOLID violations, security risks, and proposes actionable improvements. Use when performing code reviews.
serpro69/claude-toolbox/klaude-plugin/skills/review-design Skill
no license147★ repoReview design, implementation, and task documents produced by design. Evaluates document quality, internal consistency, and technical soundness. Use after design completes and before starting implement.
serpro69/claude-toolbox/klaude-plugin/skills/review-spec Skill
no license147★ repoUse after implementing tasks or mid-feature to verify code matches design docs and ensure they are in sync. Detects spec deviations, missing implementations, doc inconsistencies, and outdated docs in design and implementation documentation.
serpro69/claude-toolbox/kodex-plugin/skills/chain-of-verification Skill
no license147★ repoApply Chain-of-Verification (CoVe) prompting to improve response accuracy through self-verification. Use when complex questions require fact-checking, technical accuracy, or multi-step reasoning.
serpro69/claude-toolbox/kodex-plugin/skills/diff-skill/evals/clean-refactor/test-files/after Skill
no license147★ repoReviews tool configurations for correctness.
serpro69/claude-toolbox/kodex-plugin/skills/diff-skill/evals/clean-refactor/test-files/before Skill
no license147★ repoReviews tool configurations for correctness.
serpro69/claude-toolbox/kodex-plugin/skills/review-code Skill
no license147★ repoCode review of current git changes with an expert senior-engineer lens. Detects SOLID violations, security risks, and proposes actionable improvements. Use when performing code reviews.
serpro69/claude-toolbox/kodex-plugin/skills/review-design Skill
no license147★ repoReview design, implementation, and task documents produced by design. Evaluates document quality, internal consistency, and technical soundness. Use after design completes and before starting implement.
serpro69/claude-toolbox/kodex-plugin/skills/review-spec Skill
no license147★ repoUse after implementing tasks or mid-feature to verify code matches design docs and ensure they are in sync. Detects spec deviations, missing implementations, doc inconsistencies, and outdated docs in design and implementation documentation.
apache/magpie/skills/issue-fix-workflow Skill
145★ repoFor a single triaged `<issue-tracker>` issue confirmed as a bug or feature, draft a fix against `<upstream>` on `<default-branch>`. Produces the failing test, the smallest production change, the targeted+module test runs, and the commit. The PR is NOT opened on autopilot; the human committer reviews, signs, and pushes. Hand-back artefact summarises branch, commits, test results, and scope.
apache/magpie/skills/pairing-multi-agent-review Skill
145★ repoFan a local diff through three independent, axis-focused review passes (correctness, security, conventions), then merge the findings into a single structured report. Each pass is isolated so findings from one axis cannot suppress or bias the others. The merged report uses the same format as pairing-self-review so the developer gets a consistent signal regardless of which Agentic Pairing skill they invoke.
apache/magpie/skills/pairing-self-review Skill
145★ repoRun a structured pre-flight self-review on local changes before opening a PR. Reads the diff against a configurable base (default: the merge base of HEAD and the upstream default branch), checks correctness, security, and project conventions, and returns a structured report to the developer. No state changes, no PR, no external writes — the report is the output.