Review & quality
19,040 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
risadams/ink-and-agency/skills/developer-experience/branch-rebase Skill
no license2★ repoSafely rebase the current branch onto its upstream target (baseline, main, or master). Auto-resolves simple merge conflicts (version bumps, changelogs). Prompts for complex ones. Use when user says "rebase", "rebase branch", "rebase onto main", "update my branch", "sync with baseline", "catch up with main", or invokes /branch-rebase.
risadams/ink-and-agency/skills/developer-experience/branch-resolve-conflicts Skill
no license2★ repoUse when a git merge or rebase hits complex conflicts, or the user says "resolve conflicts" / "fix merge conflicts". Reconstructs intent, preserves both branches' goals when possible, and runs automated checks.
risadams/ink-and-agency/skills/developer-experience/git-workflow-manager Skill
no license2★ repoUse when you need to design, establish, or optimize Git workflows, branching strategies, and merge management for a project or team.
risadams/ink-and-agency/skills/developer-experience/readme-generator Skill
no license2★ repoUse when you need a maintainer-ready README built from exact repository reality, with deep codebase scanning, zero hallucination, and optional git commit/push only when explicitly requested.
risadams/ink-and-agency/skills/exec-function/rejection-sensitivity-check Skill
no license2★ repoPaste a message that stung; get a calibrated read on whether it's actually critical or neutral-but-terse. Separates evidence from interpretation to counter rejection-sensitive dysphoria. Use when user says "did they mean it that way", "is this criticism", "am I reading this wrong", "rejection check", "this stung", "rsd check", or invokes /rejection-sensitivity-check.
risadams/ink-and-agency/skills/exec-function/time-reality-check Skill
no license2★ repoCounter time blindness — you say "20 minutes" but it'll take 2 hours. Skill asks about the task, factors in your usual underestimation pattern, and offers a calibrated estimate with reasoning. Use when user says "how long will this take", "time check", "reality check", "estimate this", "am I being realistic", or invokes /time-reality-check.
risadams/ink-and-agency/skills/quality-security/ad-security-reviewer Skill
no license2★ repoUse when you need to audit Active Directory security posture, evaluate privilege escalation risks, review identity delegation patterns, or assess authentication protocol hardening.
risadams/ink-and-agency/skills/research-analysis/grill-me Skill
no license2★ repoInterview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
risadams/ink-and-agency/skills/research-analysis/grill-with-docs Skill
no license2★ repoGrilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
risadams/ink-and-agency/skills/scrum-sprint/sprint-review Skill
no license2★ repoEnd-of-sprint stakeholder report comparing the start.canvas (planning) to end.canvas (sprint close). Produces a markdown report fitting the standard SM template (Scrum Master, Sprint Accomplishments, Feature Demos, Customer Meetings, Status, Sprint Commitment, PI Confidence, Impediments). Applies team-specific overhead, wedge-balancing, and in-review overhead rules. Auto-runs a clarity-council session (statistics-expert + scrum-master + product-owner) for accomplishments/status/impediments synthesis. Use when user says "sprint review", "end of sprint report", "sprint stakeholder report", "sprint close report", or invokes /sprint-review.
risadams/ink-and-agency/skills/writing/writing-tone-check Skill
no license2★ repoReverse decoder — paste a draft message and get a read on how it will land before you send. Flags blunt, cold, accidentally passive-aggressive, or over-apologetic patterns. Use when user says "tone check", "how does this sound", "before I send this", "will this land okay", "check this draft", or invokes /writing-tone-check.
26zl/universal-agent-skills/skills/verify-changes Skill
2★ repoVerify code or configuration changes with focused tests, static checks, and diff inspection before reporting completion. Use after implementing or modifying a repository; do not use for read-only explanations or when no files changed.
batteryshark/skill-tap/skills/game-development/tetromino/tetromino-guideline-review Skill
2★ repoAudit or plan a single-player falling-tetromino implementation against an explicit historical gameplay baseline covering field geometry, seven-bag generation, controls, lock-down, scoring, spins, game-over, UI, and audio. Use for evidence-based implementation reviews or remediation plans; this is an unofficial engineering checklist, not Tetris certification.
DukeTwoCan/autonovel-agent-skills/skills/creative/autonovel-prose-review Skill
2★ repoAutonovel Phase 3b.2 — user-triggered targeted prose review. Takes a scope (e.g. 'ch 7', 'ch 7-10', 'act 2', 'the heist arc') and emits line-level critique for that scope only. NOT auto-invoked by the pipeline. Designed for the user to sit with the agent and iterate on prose quality chapter-by-chapter or arc-by-arc. Conversational: the agent presents notes and asks the user which to apply rather than auto-fixing.
Abhillashjadhav/PM-agent-OS/.claude/skills/builder-validator Skill
no license2★ repoBuild-stage skill: freeze requirements into binary criteria, generate the artifact, then self-audit against the frozen criteria verbatim before delivery. Use when the user asks for an artifact WITH requirements attached — 'draft X and check it against these requirements', 'build Y to this spec', 'generate and self-QA before showing me' — or when /pm routes a spec-bearing generation request here. Do NOT use when no requirements exist to freeze, for reviewing work the user wrote themselves, for building eval harnesses from specs (prd-to-eval), or for knowledge questions about QA.
Abhillashjadhav/PM-agent-OS/.claude/skills/pm Skill
no license2★ repoThe pm-agent-os orchestrator. Use when the user invokes /pm or hands over any product-management request — synthesizing interviews, mining feedback, mapping assumptions, tearing down a competitor, sizing an opportunity, framing jobs-to-be-done, planning research, or any multi-step product task spanning discovery, strategy, build, launch, or iterate. Classifies the request into lifecycle stage(s), invokes the matching stage skills in sequence, and blocks every output whose verification gate has not passed. Also use when the user asks to run any output past a reviewer persona — 'review as engineer/designer/executive/skeptic/customer/data-analyst/legal' — routing to the persona agents in .claude/agents/. Do NOT use for coding tasks, repo maintenance, PR reviews (/pr-review's job), or knowledge questions about PM concepts with no work item attached.
Abhillashjadhav/PM-agent-OS/.claude/skills/prd-to-eval Skill
no license2★ repoBuild-stage skill: turns a PRD or feature spec into a verification layer — binary quality gates for disqualifiers plus an anchored 1-5 rubric for tradeable qualities, with the two never mixed. Use when the user needs to define and test 'good' for a feature — 'turn this PRD into an eval', 'define good for our AI summarizer', 'build quality gates and a judge rubric', 'how do we test whether this works' — or when /pm routes a spec-bearing eval-design request here. Do NOT use to generate artifacts against frozen criteria (builder-validator), to execute an eval over outputs, for gate-vs-rubric knowledge questions, or for build/kill decisions (ai-feature-go-no-go).
Abhillashjadhav/PM-agent-OS/.claude/skills/roadmap-reality-check Skill
no license2★ repoStrategy-stage skill: audits a roadmap against unit economics — every item tagged supported or unsupported with the economic mechanism stated. Use when the user provides a roadmap plus business numbers and asks what's economically justified — 'reality-check this roadmap', 'which items pay for themselves', 'what survives contact with the P&L', 'does this lineup make economic sense' — or when /pm routes such a request here. Do NOT use to author a roadmap, to prioritize purely by customer impact without economics, to size markets (opportunity-sizer's job), or for definitions of unit-economics terms.
Abhillashjadhav/PM-agent-OS/.claude/skills/strategy-review Skill
no license2★ repoStrategy-stage skill: pressure-tests a strategy document — every weakness it raises must cite the specific line it attacks. Use when the user provides their own strategy doc, positioning memo, or plan and asks for it to be stress-tested — 'pressure-test this strategy', 'tear it apart before the board does', 'red-team this memo', 'what's weak in this one-pager' — or when /pm routes such a request here. Do NOT use to author a strategy from scratch (there must be a doc to attack), to review PRs (/pr-review), to analyze a competitor's strategy (competitor-teardown), or for knowledge questions about strategy frameworks.
sam6dvpte34/lead-generation-skill/skills/email-validator Skill
no license2★ repoValidate email addresses for deliverability — valid or invalid status, domain check, format check, risk level. Use when the user wants to clean an email list before outreach.
Google maps review lead research
sam6dvpte34/lead-generation-skill/skills/google-maps-review-lead-research Skill
no license2★ repoCollect review-based leads from Google Maps — reviewer name, review text, rating, business reviewed, contact signals. Use when the user wants to research prospects from review behavior.
Google maps reviewer contact search
sam6dvpte34/lead-generation-skill/skills/google-maps-reviewer-contact-search Skill
no license2★ repoFind contact signals from Google Maps reviewers — reviewer name, profile link, review text, rating. Use when the user wants to identify and reach frequent reviewers or customers.
sam6dvpte34/lead-generation-skill/skills/prospect-contact-verification Skill
no license2★ repoVerify contact details for a prospect list — email status, phone validity, LinkedIn match, name check. Use when the user wants to validate or clean a prospect contact list.
niksavis/basicly/.agents/skills/tool-git-delta Skill
2★ repoOne-command harness distribution for coding agents — a versioned YAML catalog projected into agent instructions, skills, and deterministic git gates.
niksavis/basicly/.agents/skills/tool-git Skill
2★ repoUse git for repository state inspection, safe staging, diff review, and history-aware change management. Trigger when the task involves commits, branches, diffs, or version control decisions.
niksavis/basicly/.agents/skills/worktree-isolation Skill
2★ repoIsolate non-trivial work in a sibling git worktree using `basicly worktree`, covering sibling placement on a harness branch, dependency + git-hook provisioning, and safe cleanup. Use when starting a unit of work that should not touch the main checkout, when parallel tracks would collide, or when deciding whether a change needs its own worktree.
pinkstrokes/self-distillation/skills/release-readiness-review Skill
2★ repoUse when judging release, deploy, launch, handoff, or deliverable readiness, especially release-ready overclaims, CI pass claims, live-smoke gaps, rollback, monitoring, user-facing, role, stale UI, ambiguous ship, data-change, or production-readiness gaps.
Fostanico/hoi4-ai-modding-skills/skills/hoi4-review-debug Skill
2★ repoDiagnose, review, improve, balance, optimize, migrate, and test existing Hearts of Iron IV mods from source through an isolated in-game run. Use for whole-mod health audits, gameplay design/balance/UX review, error.log triage, Windows crash dumps/minidumps, parser or scope bugs, broken GUI/assets/localisation, AI behavior, performance, save/lifecycle risks, compatibility, version updates, template audits, regression plans, or user-approved Steam and game testing.
jamestexas/agents/skills/pr-review-kit Skill
2★ repoCurated library of Claude Code subagents and skills (23 agents, 20 skills) with an idempotent installer that symlinks into ~/.claude. Frontmatter-driven; spec-compliant with Anthropic and Gemini schemas.
jamestexas/agents/skills/pr-review Skill
2★ repoCurated library of Claude Code subagents and skills (23 agents, 20 skills) with an idempotent installer that symlinks into ~/.claude. Frontmatter-driven; spec-compliant with Anthropic and Gemini schemas.
jamestexas/agents/skills/review-prep Skill
2★ repoCurated library of Claude Code subagents and skills (23 agents, 20 skills) with an idempotent installer that symlinks into ~/.claude. Frontmatter-driven; spec-compliant with Anthropic and Gemini schemas.
jamestexas/agents/skills/review-queue Skill
2★ repoCurated library of Claude Code subagents and skills (23 agents, 20 skills) with an idempotent installer that symlinks into ~/.claude. Frontmatter-driven; spec-compliant with Anthropic and Gemini schemas.
jamestexas/agents/skills/self-audit Skill
2★ repoCurated library of Claude Code subagents and skills (23 agents, 20 skills) with an idempotent installer that symlinks into ~/.claude. Frontmatter-driven; spec-compliant with Anthropic and Gemini schemas.
jamestexas/agents/skills/taskfile-ci-parity Skill
2★ repoCurated library of Claude Code subagents and skills (23 agents, 20 skills) with an idempotent installer that symlinks into ~/.claude. Frontmatter-driven; spec-compliant with Anthropic and Gemini schemas.
nibzard/skills/skills/git-xray Skill
2★ repoRun diagnostic git commands to assess a codebase's health before reading any code. Use this skill whenever the user asks you to understand a new codebase, audit a repo, assess technical debt, find risky code, check project health, figure out where to start reading, identify bus factor risks, or explore an unfamiliar repository. Also use it when the user asks 'what's going on in this repo', 'where are the problem areas', 'give me a health check', or 'what should I look at first'. If the user wants to understand a codebase at a strategic level before diving into code, this is the skill to use.
avivsinai/skills-marketplace/plugins/bkt/skills/bkt Skill
2★ repoCentral plugin marketplace for Claude Code and Codex
The same file is in 3 other repositories
avivsinai/skills-marketplace/plugins/yoetz/skills/yoetz Skill
2★ repoCentral plugin marketplace for Claude Code and Codex
The same file is in 1 other repository
Mokee04/ontology_research/ontology-shacl-validator Skill
no license2★ repoValidate ontology outputs through SHACL-oriented checks, structural issue reporting, and release-readiness notes tied to competency questions, evidence quality, and unresolved modeling risks.
Mokee04/ontology_research/ontology-validation-team Skill
no license2★ repoValidate a domain ontology draft using competency-question checks, SHACL-oriented structural validation, review gates, and release-readiness criteria before the ontology is treated as stable.
kinhluan/skills/.agent-skills/internal-critique Skill
2★ repoSelf-review a paper or thesis chapter before sharing with advisor or submitting. Simulates tough reviewer feedback to identify weaknesses before external review. Use when finishing a draft, preparing for advisor meeting, or doing pre-submission sanity check.
Recusive/Skills/audit-as-repo-maintainer Skill
2★ repoAudit an implementation plan through the eyes of a Repo Maintainer. Use this skill when the user says "audit as repo maintainer", "review conventions", "check code hygiene", "review the file structure", or any plan where you want to verify it follows the project's established patterns — barrel exports, file placement, naming conventions, import ordering, style reuse, code deduplication, and lint compliance. This lens catches the slow erosion of codebase health that individual feature reviews miss because each violation seems minor in isolation.
eddmann/agent-toolkit/skills/commit Skill
no license2★ repoCreate git commits using Conventional Commits format
eddmann/agent-toolkit/skills/review Skill
no license2★ repoReview code against coding guidelines and best practices
kimtth/ms-fabric-skills-dev-starter/.agents/skills/check-updates Skill
no license2★ repoCheck for skills-for-fabric marketplace updates at session start. Compares local version against GitHub releases and shows changelog if updates are available. Use when the user wants to: (1) check for skill updates, (2) see what's new in skills-for-fabric, (3) verify current version. Triggers: "check for updates", "am I up to date", "what version", "update skills", "show changelog".
kimtth/ms-fabric-skills-dev-starter/.agents/skills/microsoft-code-reference Skill
no license2★ repoLook up Microsoft API references, find working code samples, and verify SDK code is correct. Use when working with Azure SDKs, .NET libraries, or Microsoft APIs to find the right method, check parameters, get working examples, or troubleshoot errors. Catches hallucinated methods, wrong signatures, and deprecated patterns by querying official docs.
chaunsin/agent-skills/skills/pre-release-review Skill
2★ repoProduction pre-release code review and deploy-readiness audit for web/backend services. Use this skill whenever the user mentions release audit, pre-release review, production deploy, deploy readiness, go-live review, code release, publishing to production, tag release, CI/CD before production, checking a PR before release, or asking whether code is safe to ship. This skill compares a PR or git range against the previous release point and looks for missing migrations, environment/config changes, seeded data, cache work, queues, object storage assets, credentials leaks, service deployment order, rollback risk, and other production launch blockers. Prefer this skill even when the user only says "review this release" or "check production risks".
troyjthomas/ios-agent-skills/skills/device-testing Skill
2★ repoTest your app on real devices, catch edge cases, and verify accessibility before shipping. Use this skill after polish is complete and you're preparing for TestFlight or App Store submission. This is the final quality gate before real users touch the app.
troyjthomas/ios-agent-skills/skills/git-workflow Skill
2★ repoGit conventions for parallel Claude Code workstreams in Conductor. Covers branching strategy, merge order, conflict prevention, shared file protection, and the checkpoint pattern. Use this skill throughout the build phase, especially when running multiple Conductor workspaces. Prevents the merge conflicts and corrupted state that kill momentum.
troyjthomas/ios-agent-skills/skills/verification-loop Skill
2★ repoHow to actually prove a UI change works before claiming it does. Covers AX-coordinate snapshots over screenshots, tap-by-label over coordinates, simulator state resets between iterations, and the build → screenshot → AX → math-check loop. Use this skill alongside testing-strategy whenever you're verifying a UI fix on simulator. Required reading before claiming any visual fix is "done."
yu-iskw/meta-agent-skills/.claude/skills/lint-fix Skill
no license2★ repoIteratively run linters, apply auto-fixes, and resolve remaining issues using Trunk.
secondorderai/ouroboros/.agents/skills/grill-me Skill
2★ repoInterview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
The same file is in 1 other repository
secondorderai/ouroboros/.agents/skills/ou-features-audit Skill
2★ repoAudit implemented Ouroboros features against requirements, PRDs, tickets, GitHub issues, or acceptance criteria to find missing, partial, incorrect, or unverifiable work. Use when the user asks to audit a feature, verify implementation completeness, compare code to requirements, check acceptance criteria, run a gap analysis, determine what is left to build, check whether a ticket is done, audit against a PRD/spec, or asks whether recent work in the Ouroboros codebase matches its requirements. Do NOT use for creating PRDs, generating tickets, implementing tickets, broad full-codebase review, or general bug triage.
secondorderai/ouroboros/.agents/skills/ou-full-code-review Skill
2★ repoPerform a comprehensive full-codebase code review using specialized parallel agents. Use this skill whenever the user asks for a "full code review", "codebase review", "review everything", "audit the code", "code health check", or any request to review the entire project (not just a PR or single file). Also trigger when the user says things like "what's wrong with this codebase", "find all the issues", "review all my code", or "comprehensive review". This is specifically for whole-codebase analysis, not single-file or PR-scoped reviews.
ckorhonen/swe-skills/skills/change-validation-planner Skill
2★ repoPlans the narrowest trustworthy validation path for a scoped code change or diff. Use when a user asks what to run before merging, how to validate a specific change, whether the current checks are enough, or wants a bounded command order from narrow to broad. Do NOT use for writing tests, fixing the code change itself, broad QA sweeps, or generic debugging that needs root cause analysis.
ckorhonen/swe-skills/skills/pr-risk-review Skill
2★ repoReviews open or draft pull requests for engineering risk before merge, focusing on missing validation, hidden coupling, rollout and rollback gaps, migrations, feature flags, and other agent-safe next actions. Use when a user says `review this PR for risk`, `pre-merge review`, `is this PR safe to merge`, or asks for a risk-focused PR review. Do NOT use for post-merge production monitoring, broad code smell review, or commit-scoped bug hunting.
ckorhonen/swe-skills/skills/recent-commit-bug-hunt Skill
2★ repoScans recent commits in one or more repositories, identifies likely bugs using concrete repo evidence only, and proposes tightly scoped remediation sessions. Use when a user says `scan recent commits for bugs`, `what did I probably break`, `review yesterday's changes for regressions`, or asks for a commit-scoped bug hunt. Do NOT use for a broad code health review, full security audit, or speculative bug hunting with no repo or time scope.
scalekit-inc/skills/skills/mcp-auth-expressjs-scalekit Skill
no license2★ repoAdd Scalekit OAuth authentication to an Express.js MCP server (TypeScript). Supports two modes: scaffold a new server from scratch, or retrofit an existing Express app. Implements /.well-known/oauth-protected-resource for MCP client discovery, a Bearer-token validation middleware using @scalekit-sdk/node (audience check), and a POST / MCP endpoint using StreamableHTTPServerTransport.
lliangcol/llm-plugins-fusion/nova-plugin/skills/nova-review Skill
2★ repoUnified canonical review Skill. Apply LEVEL and MODE to review depth and output shape; no code modification.
harshitsinghbhandari/domain-expansion/skills/boundary-bug-hunter Skill
no license2★ repoAggressive user-flow and boundary-bug analysis on a diff or branch. Auto-detects entry points, traces flows through changed code, finds every seam (cross-module calls, serialization, file I/O, shared state, schema versioning, network/IPC), and refuses to mark the work complete until each unverified boundary has a real round-trip test or an explicit written out-of-scope record persisted in an audit file. Use whenever the user says "boundary check", "seam check", "round-trip check", "flow boundaries", "user-flow check", "before merge", "is this safe to ship", "pre-merge gate", "boundary bugs", "verify the joins", or asks to validate cross-module joins, producer/consumer contracts, or end-to-end coverage of a change. Also use as a final gate from pr-review on any diff that touches more than one file, module, or process. Be pushy. Most surviving production bugs live at seams, not inside units — if the diff crosses any boundary, this skill almost certainly applies.
harshitsinghbhandari/domain-expansion/skills/pr-review Skill
no license2★ repoComprehensive PR review focusing on code quality, test coverage, security, backward compatibility, and what CI cannot check. Use when reviewing PRs, when asked to review code changes, or when the user mentions "review PR", "code review", or "check this PR".