agentsclimarketplace

Review & quality

19,181 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

  • Requesting code review

    kevinnft/ai-agent-skills/skills/superpowers/requesting-code-review Skill

    13★ repo

    Use when completing tasks, implementing major features, or before merging to verify work meets requirements

  • Using git worktrees

    kevinnft/ai-agent-skills/skills/superpowers/using-git-worktrees Skill

    13★ repo

    Use 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

  • Verification before completion

    kevinnft/ai-agent-skills/skills/superpowers/verification-before-completion Skill

    13★ repo

    Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

  • Dotnet biome

    Postpartum-genushyacinthus29/dotnet-skills/skills/dotnet-biome Skill

    13★ repo

    Use Biome in .NET repositories that ship Node-based frontend assets and want a fast combined formatter-linter-import organizer for JavaScript, TypeScript, CSS, JSON, GraphQL, or HTML. Use when a repo prefers a modern all-in-one CLI over a larger ESLint plus Prettier style stack.

  • Dotnet code review

    Postpartum-genushyacinthus29/dotnet-skills/skills/dotnet-code-review Skill

    13★ repo

    Review .NET changes for bugs, regressions, architectural drift, missing tests, incorrect async or disposal behavior, and platform-specific pitfalls before you approve or merge them.

  • Dotnet eslint

    Postpartum-genushyacinthus29/dotnet-skills/skills/dotnet-eslint Skill

    13★ repo

    Use ESLint in .NET repositories that ship JavaScript, TypeScript, React, or other Node-based frontend assets. Use when a repo needs a configurable CLI lint gate for frontend correctness, import hygiene, unsafe patterns, or framework-specific rules.

  • Dotnet mcaf feature spec

    Postpartum-genushyacinthus29/dotnet-skills/skills/dotnet-mcaf-feature-spec Skill

    13★ repo

    Apply MCAF feature-spec guidance to create or update a feature spec under `docs/Features/` with business rules, user flows, system behaviour, verification, and Definition of Done. Use when the user asks for a feature spec, executable requirements, acceptance criteria, behaviour documentation, or a pre-implementation plan for non-trivial behaviour changes.

  • Dotnet mcaf human review planning

    Postpartum-genushyacinthus29/dotnet-skills/skills/dotnet-mcaf-human-review-planning Skill

    13★ repo

    Apply MCAF human-review-planning guidance for a large AI-generated code drop by reading the target area, tracing the natural user and system flows, identifying the riskiest boundaries, and prioritizing the files a human should inspect first. Use when the codebase is too large to review line-by-line and you need a practical review sequence plus a prioritized file list.

  • Dotnet mcaf source control

    Postpartum-genushyacinthus29/dotnet-skills/skills/dotnet-mcaf-source-control Skill

    13★ repo

    Apply MCAF source-control guidance for repository structure, branch naming, merge strategy, commit hygiene, and secrets-in-git discipline. Use when bootstrapping a repo, tightening PR flow, or documenting branch and release policy.

  • Grill with docs requiem

    CheckPickerUpper/skills/skills/productivity/grill-with-docs-requiem Skill

    13★ repo

    A high-judgment design interview that sharpens plans in useful batches and records settled domain language and ADRs as the conversation progresses.

  • Design critique facilitation

    Dragoon0x/everything-design-taste/skills/design-critique-facilitation Skill

    13★ repo

    Running effective design critiques, structured feedback sessions, and group review processes.

  • Design critique

    Dragoon0x/everything-design-taste/skills/design-critique Skill

    13★ repo

    Structured frameworks for giving and receiving design feedback that makes work better, not just different.

  • Design portfolio review

    Dragoon0x/everything-design-taste/skills/design-portfolio-review Skill

    13★ repo

    Reviewing design portfolios, portfolio structure advice, and evaluating design candidates.

  • Code review

    laragentic/agents/tests/Fixtures/test-skills/code-review Skill

    no license13★ repo

    Analyze code for security, performance, and best practices

  • Commit

    kriscard/Skills/skills/dev/commit Skill

    13★ repo

    Creates semantic git commits with conventional commit format, stages selected changes safely, and optionally pushes to remote after explicit approval. Handles pre-commit hooks and writes meaningful commit messages. Use when the user says "commit", "push changes", "save to git", "commit this", or wants to create a git commit — even if they just say "save my work."

  • Pr review

    kriscard/Skills/skills/dev/pr-review Skill

    13★ repo

    Bug-first, evidence-only PR review with guidance-scoped specialist passes for security, correctness, architecture, React patterns, and accessibility. Use when the user says "review this PR", "review my changes", "review the diff", or mentions a PR number. Prefers silence over speculative findings.

  • Review

    kriscard/Skills/skills/dev/review Skill

    13★ repo

    Bug-first, evidence-only review for code changes: find production-impacting security, correctness, reliability, performance, and maintainability issues. Use after writing or modifying code, when reviewing diffs or PRs, or when the user asks "review this", "check this code", mentions security, code quality, or performance. Enforces project guidance when available and prefers silence over speculative findings.

  • Check communication

    kriscard/Skills/skills/productivity/check-communication Skill

    13★ repo

    Reviews draft communication before sending: Slack, email, PR comments, status updates, proposals, feedback, and pushback. Use when the user asks if a message sounds right, wants a rewrite, or pastes a draft for tone, clarity, buried asks, passive aggression, length, or next-step review.

  • Spawning reviewers

    smixs/disruptor-skills/skills/spawning-reviewers Skill

    13★ repo

    Use when dispatching one or more reviewer agents for an adversarial second opinion on any artifact — code, a design, a document, a plan, a research report, a deck. Especially when a prior review felt like a rubber-stamp or parroted the prompt's framing, when findings were vague with no locations, when tempted to tell the reviewer what to expect or where to look, or when reviewing something assembled from multiple sources (a merge, a consolidation). Any domain.

  • Unvibe review

    smixs/disruptor-skills/skills/unvibe-review Skill

    13★ repo

    Use when a project, system, document, or workflow feels bloated, over-engineered, tangled, or fragile despite "working," or when rounds of iteration/review have only ever ADDED and never removed — to find what can be cut, unified, or reframed. Any domain (code, writing, research, video, analysis, ops, decks). Especially when "every part seems necessary" but the whole feels heavy.

  • Public code review

    olgaiv39/claude-oss-skills/skills/public-code-review Skill

    13★ repo

    Review the current diff or a specified set of files as public open-source code before publishing or merging. Use to check code quality, public-repository safety (secrets and private data), documentation trustworthiness, provenance, onboarding, and maintainability. Reports grouped findings; does not fix them unless asked.

  • Release deploy

    olgaiv39/claude-oss-skills/skills/release-deploy Skill

    13★ repo

    Prepare a public open-source project for release and deploy it to a detected target. Use at a release or submission boundary to verify setup, docs, secrets, tests, lint, build, and licenses, then follow the target-specific deployment path. Runs expensive checks sequentially. Never publishes, tags, commits, pushes, or deploys without explicit user intent.

  • Test and debug

    olgaiv39/claude-oss-skills/skills/test-and-debug Skill

    13★ repo

    Diagnose and repair a failing test, build, or runtime error in a public open-source project using the narrowest reproduction and validation. Use when something is broken and the cause is not yet known. Classifies the failure, isolates a reproduction, applies the smallest fix, and confirms with a targeted check. Does not add features.

  • Kybernetes verify run

    pariyar07/kybernetes/skills/kybernetes-verify-run Skill

    13★ repo

    Independently test a completion claim against DONE with explicit coverage, provenance, gaps, rerun instructions, and rejection authority.

  • Bug bash

    Flagrare/agent-skills/plugins/flagrare/skills/bug-bash Skill

    no license12★ repo

    Programmatic bug bashing, ingest a prescribed test plan (Notion, markdown, pasted spec), drive a real running system (browser via Chrome DevTools / Playwright MCP, backend via API tools when relevant), run every prescribed case with evidence, then do exploratory passes (viewports, multi-actor flows, codebase-driven concerns, additional context like meeting transcripts) without ever claiming a bug it didn't itself reproduce. Lands results in a local MD file by default, optionally writes back to the source (Notion bug DB, test case Eng QA columns, etc.) in the user's voice. Use whenever the user says 'bug bash', 'QA this feature', 'run the test cases', 'go through this test plan', 'verify these scenarios', 'do a bash on X', when they hand over a Notion test case page, or any time programmatic end-to-end verification of a feature against a checklist is needed. Make sure to use this skill even when the user just says 'test this Notion page' or 'check these scenarios', anything that smells like running someone else's prescribed test plan against a live system.

  • Daily code review

    Flagrare/agent-skills/plugins/flagrare/skills/daily-code-review Skill

    no license12★ repo

    Generate a daily code review report showing stale PRs, items needing your attention, and active work for your team. Use whenever the user asks for a PR report, code review status, daily standup prep, team PR overview, "what needs review", "what's stale", "show me open PRs", "daily review", "PR check", "review report", "what should I look at today", or any question about tracking pull request activity across a team or pod. Also trigger when the user mentions a specific pod name that matches a saved config.

  • Design review

    Flagrare/agent-skills/plugins/flagrare/skills/design-review Skill

    no license12★ repo

    Evaluate and refine UI the way a senior product designer would, visual hierarchy, spacing and rhythm, typographic scale, legibility, information density, alignment, and restraint, then apply the highest-leverage fixes. Use this skill WHENEVER the user says a UI / page / screen / component feels 'clunky', 'packed', 'cramped', 'busy', 'off', 'amateur', 'cluttered', or 'needs polish'; when they ask to 'improve the design / layout / hierarchy / spacing / legibility', 'make this look designed / professional', 'apply design principles', 'clean this up', 'review the design', or want a 'senior designer' / 'senior product designer' pass; and proactively after building any non-trivial UI, to critique and tighten it before moving on. Grounded in the design canon (Dieter Rams, Edward Tufte, the Gestalt principles, the Vignelli Canon, Nielsen's heuristics) and the Refactoring UI playbook. It respects and extends the project's existing brand / design system first, runs a mandatory system coverage inventory (undesigned groups and unspent brand personality are automatic findings, not just visual excess), reviews the whole surface across all states rather than the recent diff, and documents any missing pattern before building it. When a screen 'lacks personality' it benchmarks named personality-forward references (e.g. PostHog, Duolingo) and designs from them rather than rearranging what exists. Works on existing UI code (improves it in place) or on a screenshot / description. Distinct from a usability/UX audit (this is visual / product-design craft) and from code review (this is design, not correctness).

  • Five lens review

    Flagrare/agent-skills/plugins/flagrare/skills/five-lens-review Skill

    no license12★ repo

    Evaluate a product-direction question through five expert lenses, Senior PM, Senior Product Engineer, Senior Product Designer, Senior Design Engineer, and a realistic end user, then synthesize the conclusions into a single recommendation. Use whenever a user-facing decision has multiple competing constraints (lifecycle behavior, data-model trade-offs, destructive actions, UX choices that touch retention) and a one-perspective answer would miss something. Trigger phrases: 'what should we do about X', 'what happens when the user Y', 'how should we handle this case', 'I need to think through this', 'help me decide', 'we don't have answers for these questions', 'spawn personas', 'evaluate from all POVs'. Especially use this when the user is mid-implementation and surfaces an edge case the spec didn't cover, that's when single-perspective reasoning silently locks in the wrong default.

  • Implementation review

    Flagrare/agent-skills/plugins/flagrare/skills/implementation-review Skill

    no license12★ repo

    Pre-commit quality gate. Invoke before every git commit, after /flagrare:staleness-audit. Seven checks, plan gaps, use-case coverage gaps, missing test scenarios, test philosophy violations (Kent Dodds Testing Trophy), SOLID violations, Clean Code violations, and security vulnerabilities. Each check is delegated to a parallel subagent. Surfaces findings before they land in history. Also invoke when the user says review this, am I done, did I miss anything, or check the quality.

  • Open pr

    Flagrare/agent-skills/plugins/flagrare/skills/open-pr Skill

    no license12★ repo

    Open a pull request that follows the repo's conventions. Reads the PR template from .github/PULL_REQUEST_TEMPLATE.md, fills it with contextualized content (not enumerations), links tracker tickets, writes testing notes, and uses /flagrare:write-docs style for the description. Use when the user says 'open a pr', 'create pr', 'push and pr', 'submit this', 'open pull request', or any variation. Also triggers when code is ready to ship and the user wants to get it reviewed.

  • Pr reviewer

    Flagrare/agent-skills/plugins/flagrare/skills/pr-reviewer Skill

    no license12★ repo

    Claude Code skills that wrap your full dev cycle — ticket intake, ATDD planning, code review, doc-drift audits, PR writing, and changelogs.

  • Release check

    Flagrare/agent-skills/plugins/flagrare/skills/release-check Skill

    no license12★ repo

    Post-commit gate. Invoke after every commit (right after /flagrare:staleness-audit). Checks whether a release is due, and if so, proposes a semver bump and a value-focused CHANGELOG entry modeled on Valve's Dota 2 patch notes, describing what the user gains, never what was refactored. Acts on approval.

  • Staleness audit

    Flagrare/agent-skills/plugins/flagrare/skills/staleness-audit Skill

    no license12★ repo

    Pre-commit audit. Invoke before every git commit. Diffs the staged change against the repo's "canaries" (README, decision log, roadmap, public API, doc comments, release notes, test discipline) and surfaces anything that's drifted out of sync. Updates the obvious drifts in place; flags judgement calls for the operator.

  • Wrap up

    Flagrare/agent-skills/plugins/flagrare/skills/wrap-up Skill

    no license12★ repo

    Post-implementation quality gate. Runs automated checks (tests, lint, types), invokes /flagrare:implementation-review for the seven-check parallel review, then performs additional SOLID and Clean Code review on any findings not covered. Use when the user says 'wrap up', 'review changes', 'check my work', 'am I done', or after completing an implementation task.

  • Code review

    iuliandita/skills/skills/code-review Skill

    12★ repo

    · Review code for correctness: bugs, edge cases, races, leaks, regressions. Triggers: 'review', 'code review', 'find bugs', 'check this', 'spot check', 'sanity check'. Not for style/slop (anti-slop) or vulnerabilities (security-audit).

  • Deep grill

    iuliandita/skills/skills/deep-grill Skill

    12★ repo

    · Grill a plan before building: clarify the decision tree, then attack it. Triggers: 'grill me', 'deep grill', 'stress-test this plan', 'poke holes', 'what did I miss'. Not for existing code (code-review) or decision red-team (jekyll-hyde).

  • Dev cycle

    iuliandita/skills/skills/dev-cycle Skill

    12★ repo

    · Run dev workflow: branch, implement, lint/test, review, docs, PR, merge, release. Triggers: 'start working', 'kick off', 'wrap up', 'ship this', 'ready to ship'. Not for single git ops (use git).

  • Frontend design

    iuliandita/skills/skills/frontend-design Skill

    12★ repo

    · Build/critique frontend UIs with taste, rejecting AI design tells. Mobile-first, touch-aware, dark+light. Triggers: 'frontend', 'ui', 'ux', 'css', 'tailwind', 'landing page', 'design review'. Not for code logic (code-review).

  • Full review

    iuliandita/skills/skills/full-review Skill

    12★ repo

    · Run 4 fixed audits in parallel (code-review, anti-slop, security-audit, update-docs) as a quick quality gate. Triggers: 'full review', 'run all checks', 'full check', 'quad audit', 'review before merge'. For deep coverage, use deep-audit.

  • Git

    iuliandita/skills/skills/git Skill

    12★ repo

    · Handle git branches, commits, remotes, conflicts, hooks, signing, releases, PR/MR workflows. Triggers: 'git', 'commit', 'branch', 'merge', 'rebase', 'tag', 'push', 'PR', 'MR', 'gh', 'glab'.

  • Tidymodels review patterns

    choxos/BiostatAgent/plugins/r-tidy-modeling/skills/tidymodels-review-patterns Skill

    12★ repo

    Review patterns for tidymodels workflows, including leakage, resampling, tuning, metrics, and reproducibility.

  • Finishing a development branch

    JustMichael-80/MasterVault/skills/superpowers/skills/finishing-a-development-branch Skill

    12★ repo

    Use 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

    The same file is in 5 other repositories

  • Receiving code review

    JustMichael-80/MasterVault/skills/superpowers/skills/receiving-code-review Skill

    12★ repo

    Use 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

    The same file is in 6 other repositories

  • Requesting code review

    JustMichael-80/MasterVault/skills/superpowers/skills/requesting-code-review Skill

    12★ repo

    Use when completing tasks, implementing major features, or before merging to verify work meets requirements

    The same file is in 4 other repositories

  • Using git worktrees

    JustMichael-80/MasterVault/skills/superpowers/skills/using-git-worktrees Skill

    12★ repo

    Use 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

    The same file is in 5 other repositories

  • Verification before completion

    JustMichael-80/MasterVault/skills/superpowers/skills/verification-before-completion Skill

    12★ repo

    Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

    The same file is in 40 other repositories

  • Dolphindb hfdataimport check env

    dolphindb/DolphinX_Skill/dolphindb-hfdataimport/dolphindb-hfdataimport-check-env Skill

    no license12★ repo

    检查通联数据/CsmarData 导入 DolphinDB 的前置环境是否满足,自动修复可修复的问题

  • Dolphindb tushare check env

    dolphindb/DolphinX_Skill/dolphindb-tushare-import/dolphindb-tushare-check-env Skill

    no license12★ repo

    检查 Tushare 数据导入 DolphinDB 的前置环境,确认 httpClient 插件和py插件(可选)以及 easy_tushare 模块可用。

  • Review swarm

    alonbaron/claude-skills/skills/review-swarm Skill

    12★ repo

    Local, free, multi-specialist review of a diff: parallel Claude subagents (correctness, security/trust boundaries, data/perf, architecture-altitude, ponytail-simplicity, tests/failure paths), adversarial verification, dedup, ranked file:line report. Use proactively when asked to review, check, or assess a diff, branch, or PR — and after any non-trivial implementation, before the PR. Also on "review-swarm", "swarm review", "deep review". Not for trivial diffs, not when asked to fix rather than review, not when security alone is the whole ask (built-in "security-review"), and not when "/code-review" is named explicitly.

  • Academic paper reviewer

    serejaris/kimi-skills/skills/academic-paper-reviewer Skill

    12★ repo

    Simulates academic peer review, evaluating papers across Originality, Methodology, Results, and Writing to provide Major/Minor Revision recommendations with actionable feedback. Triggers when a user asks to "review my paper," "simulate peer review," or "give my paper a peer review.

    The same file is in 1 other repository

  • Batch download

    serejaris/kimi-skills/skills/batch-download Skill

    12★ repo

    Multi-agent batch download and data collection orchestration. Use this skill whenever the task requires discovering, validating, and downloading multiple files or datasets from the web — batch report downloads, multi-source data collection, structured web scraping, file archival, or any task demanding parallel discovery and retrieval with verification. This skill enforces plan-first decomposition, parallel sub-agent delegation, evidence-based URL discovery, strict output validation, and structured result integration. Do NOT use for: single file download, simple API calls, tasks that don't involve web discovery or file retrieval.

  • Cite style converter

    serejaris/kimi-skills/skills/cite-style-converter Skill

    12★ repo

    Convert academic citations between APA, MLA, IEEE, and Harvard styles with batch processing and format validation. Trigger when users ask to convert, check, or fix their references, mention specific citation styles, or talk about their bibliography.

  • Compliance review planner

    serejaris/kimi-skills/skills/compliance-review-planner Skill

    12★ repo

    为特定业务场景构建合规检查清单,覆盖 GDPR、个保法、广告法、数据安全法等主要法规,输出包含检查项、法规依据、风险等级和整改建议的结构化清单。当用户描述业务场景并提及合规检查、合规清单、GDPR 检查、个保法合规、广告法审查、数据合规、隐私合规、compliance checklist、数据出境评估、个人信息保护、合规自查、隐私影响评估(PIA/DPIA)、上线前合规审查或询问“这个功能合不合规”时触发。

  • Conventional commit gen

    serejaris/kimi-skills/skills/conventional-commit-gen Skill

    12★ repo

    Analyzes git diff to generate commit messages following the Conventional Commits spec, with automatic scope detection and commit type inference. Trigger when users ask to write or generate a commit message, mention Conventional Commits, git commits, standardized commits, scope detection, or phrases like 'help me write a commit message'.

  • Earnings review note

    serejaris/kimi-skills/skills/earnings-review-note Skill

    12★ repo

    Generate professional sell-side earnings review reports for quarterly or annual results, producing PDF/DOCX/PPTX documents with EPS analysis, guidance review, and variance tables. Triggered when users request an earnings review, need a quarterly wrap, ask for a beat/miss analysis, or mention summarizing an earnings call for any public company.

  • Equity earnings review

    serejaris/kimi-skills/skills/equity-earnings-review Skill

    12★ repo

    生成专业的卖方股票财报点评文档,覆盖上市公司季度或年度业绩回顾。输出内容包括EPS超预期/不及预期分析、业绩指引点评、盈利预测调整、估值更新、分部业务评述,以及实际业绩与市场一致预期的对比分析,并可整理财报电话会要点形成结构化报告。支持任意行业和公司。当用户请求撰写财报点评、业绩总结、财务模型差异分析,或提及EPS超预期、业绩指引、盈利预测调整、估值更新等关键词时触发。

  • Git repo audit

    serejaris/kimi-skills/skills/git-repo-audit Skill

    12★ repo

    深度分析 Git 仓库历史,识别高频变更的热点文件、分析代码的实际贡献归属关系、并扫描历史提交中的密钥泄露等安全隐患。当用户提及分析仓库、查看代码归属、寻找热点文件或安全风险扫描,或询问团队协作、代码审查分配、技术债务与安全审计等关键词时触发。

  • Glab check update

    serejaris/kimi-skills/skills/gitlab-cli-guide/glab-check-update Skill

    12★ repo

    检查 glab CLI 更新并查看最新版本信息。适用于检查 glab 是否为最新版本或查找可用更新。触发词:更新 glab、检查版本、glab 版本、CLI 更新。

  • Glab mr

    serejaris/kimi-skills/skills/gitlab-cli-guide/glab-mr Skill

    12★ repo

    创建、查看、管理、批准和合并 GitLab merge request(合并请求)。适用于从分支/议题创建 MR、审查、批准、添加评论、解决讨论线程、本地检出、查看差异、变基、合并或管理状态等场景。触发关键词:merge request、MR、pull request、PR、审查、批准、合并、解决线程。

  • Glab attestation

    serejaris/kimi-skills/skills/gitlab-cli-skills/glab-attestation Skill

    12★ repo

    Work with GitLab attestations for software supply chain security including artifact verification and provenance. Use when verifying software artifacts, managing attestations, or working with supply chain security. Triggers on attestation, verify artifact, provenance, supply chain security.