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

  • Receiving code review

    galyarderlabs/galyarder-framework/integrations/windsurf/skills/receiving-code-review Skill

    20★ 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

  • Requesting code review

    galyarderlabs/galyarder-framework/integrations/windsurf/skills/requesting-code-review Skill

    20★ repo

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

  • Review

    galyarderlabs/galyarder-framework/integrations/windsurf/skills/review Skill

    20★ repo

    Review Playwright tests for quality. Use when user says "review tests", "check test quality", "audit tests", "improve tests", "test code review", or "playwright best practices check".

  • Security reviewer

    galyarderlabs/galyarder-framework/integrations/windsurf/skills/security-reviewer Skill

    20★ repo

    Use when legacy prompts or older framework flows reference `security-reviewer` and you need the modern runtime to resolve that capability cleanly.

  • Using git worktrees

    galyarderlabs/galyarder-framework/integrations/windsurf/skills/using-git-worktrees Skill

    20★ repo

    Use when legacy prompts or older framework flows reference `using-git-worktrees` and you need the modern runtime to resolve that capability cleanly.

  • Verification before completion

    galyarderlabs/galyarder-framework/integrations/windsurf/skills/verification-before-completion Skill

    20★ 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

  • Adversarial reviewer

    galyarderlabs/galyarder-framework/skills/adversarial-reviewer Skill

    20★ repo

    Use when a plan, feature, or launch needs an explicit adversarial pass to find weak assumptions, abuse cases, or strategic blind spots before execution.

    The same file is in 1 other repository

  • Code review expert

    galyarderlabs/galyarder-framework/skills/code-review-expert Skill

    20★ repo

    Use when legacy prompts or older framework flows reference `code-review-expert` and you need the modern runtime to resolve that capability cleanly.

    The same file is in 1 other repository

  • Code reviewer

    galyarderlabs/galyarder-framework/skills/code-reviewer Skill

    20★ repo

    Use when legacy prompts or older framework flows reference `code-reviewer` and you need the modern runtime to resolve that capability cleanly.

    The same file is in 1 other repository

  • Contract review

    galyarderlabs/galyarder-framework/skills/contract-review Skill

    20★ repo

    Analyze and red-flag contracts systematically, identifying risks, unfavorable terms, and negotiation opportunities

    The same file is in 1 other repository

  • Doc maintenance

    galyarderlabs/galyarder-framework/skills/doc-maintenance Skill

    20★ repo

    Audit top-level documentation (README, SPEC, PRODUCT) against recent git history to find drift shipped features missing from docs or features listed as upcoming that already landed. Proposes minimal edits, creates a branch, and opens a PR. Use when asked to review docs for accuracy, after major feature merges, or on a periodic schedule.

    The same file is in 1 other repository

  • Finishing a development branch

    galyarderlabs/galyarder-framework/skills/finishing-a-development-branch Skill

    20★ 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

  • Review

    galyarderlabs/galyarder-framework/skills/playwright-pro/skills/review Skill

    20★ repo

    Review Playwright tests for quality. Use when user says "review tests", "check test quality", "audit tests", "improve tests", "test code review", or "playwright best practices check".

  • Pr review expert

    galyarderlabs/galyarder-framework/skills/pr-review-expert Skill

    20★ repo

    Use when legacy prompts or older framework flows reference `pr-review-expert` and you need the modern runtime to resolve that capability cleanly.

  • Receiving code review

    galyarderlabs/galyarder-framework/skills/receiving-code-review Skill

    20★ 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

  • Requesting code review

    galyarderlabs/galyarder-framework/skills/requesting-code-review Skill

    20★ repo

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

  • Security reviewer

    galyarderlabs/galyarder-framework/skills/security-reviewer Skill

    20★ repo

    Use when legacy prompts or older framework flows reference `security-reviewer` and you need the modern runtime to resolve that capability cleanly.

  • Using git worktrees

    galyarderlabs/galyarder-framework/skills/using-git-worktrees Skill

    20★ repo

    Use when legacy prompts or older framework flows reference `using-git-worktrees` and you need the modern runtime to resolve that capability cleanly.

  • Verification before completion

    galyarderlabs/galyarder-framework/skills/verification-before-completion Skill

    20★ 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

  • Code review

    helderberto/agent-skills/skills/code-review Skill

    20★ repo

    Review a GitHub Pull Request for bugs, security, performance, and code quality. Use when user asks to review a PR or wants pull request feedback. Don't use for reviewing local uncommitted changes, creating new PRs, or merging branches.

  • Commit

    helderberto/agent-skills/skills/commit Skill

    20★ repo

    Group unstaged changes into atomic commits by concern, following repository style. Use when user asks to "commit", "create a commit", "commit changes", or "/commit". Don't use for pushing (that belongs to /ship) or creating pull requests.

  • Create pull request

    helderberto/agent-skills/skills/create-pull-request Skill

    20★ repo

    Create a GitHub pull request — fills the repo's PR template, conventional-commit title, ticket refs. Draft mode via `--draft`.

  • Grill me

    helderberto/agent-skills/skills/grill-me Skill

    20★ repo

    A relentless interview to sharpen a plan or design. Use when the user wants to stress-test a plan, pressure-test assumptions, or says "grill me" or "poke holes in this". Don't use for code review (use /code-review) or gathering initial requirements (use /spec).

  • I18n

    helderberto/agent-skills/skills/i18n Skill

    20★ repo

    Audit internationalization coverage and find hardcoded strings. Use when user asks to "check i18n", "/i18n", "find hardcoded strings", "check translations", or wants to verify translation coverage. Don't use for backend string extraction, non-frontend code, or projects without an i18n library.

  • Lint

    helderberto/agent-skills/skills/lint Skill

    20★ repo

    Run linting and formatting checks. Use when user asks to "run linter", "/lint", "check linting", "fix lint errors", or requests code linting/formatting. Don't use for running tests or type-checking only.

  • Resolving merge conflicts

    helderberto/agent-skills/skills/resolving-merge-conflicts Skill

    20★ repo

    Resolve an in-progress git merge or rebase conflict by recovering each side's intent, then finishing the merge. Use when a merge or rebase is mid-conflict, git reports conflicted files, or the user asks to resolve conflicts. Don't use for preventing future conflicts, general git operations, or rewriting history where nothing is conflicted.

  • Review

    helderberto/agent-skills/skills/review Skill

    20★ repo

    Orchestrated REVIEW phase — fan out parallel, read-only reviewers over a diff (scope-detected audit skills AND independent agent lenses), then consolidate into one severity-ranked verdict. Use for a full pre-ship review, "review/validate this PR", or "spawn agents to review". Don't use to implement fixes (use /build or /tdd), for a single focused audit or one-lens pass (call it directly, e.g. /a11y-audit, /code-review), or to triage existing reviewer comments (use /triage-review).

  • Safe repo

    helderberto/agent-skills/skills/safe-repo Skill

    20★ repo

    Check for sensitive data in repository. Use when user asks to "check for sensitive data", "/safe-repo", or wants to verify no company/credential data is in the repository. Use `--diff` mode to scope to staged + unstaged changes only (e.g., before commit). Don't use for general code review, adding .gitignore entries, or scanning non-git directories.

  • Setup pre commit

    helderberto/agent-skills/skills/setup-pre-commit Skill

    20★ repo

    Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests. Use when user asks to "add pre-commit hooks", "setup husky", "setup pre-commit", "configure lint-staged", or wants commit-time formatting/typechecking/testing. Don't use for running linters manually or writing tests.

  • Test

    helderberto/agent-skills/skills/test Skill

    20★ repo

    VERIFY phase — prove the code works. Run validation (lint, types, tests) plus coverage on changes, and when a plan exists verify its checkboxes against the codebase. Use after /build, when the user asks to verify, test, or confirm work holds up, or to check plan progress. Don't use to implement phases (use /build) or write new tests from scratch (use /tdd).

  • Triage review

    helderberto/agent-skills/skills/triage-review Skill

    20★ repo

    Fetch unresolved review comments on a GitHub PR (Copilot bot + human reviewers), verify each against the current code, and classify as Address / Skip / Optional / Discuss with a one-line rationale. Use when the user asks which review comments to address, to triage Copilot/reviewer feedback, sort signal from noise on a PR, or decide what makes sense to fix and what not. Don't use to reply to or resolve threads (out of scope — this is read-only), or to generate a fresh review (use /code-review or /review).

  • Validate code

    helderberto/agent-skills/skills/validate-code Skill

    20★ repo

    Validate code quality: auto-fix formatting/lint, verify types, run tests. Use when user asks to "validate code", "/validate-code", "check code", or wants to validate before committing. Don't use for committing, pushing, or writing new tests.

  • Visual review

    helderberto/agent-skills/skills/visual-review Skill

    20★ repo

    Render a GitHub Pull Request diff as a self-contained HTML page where each changed hunk is annotated with a software-principle explanation and a suggested simplification. Use when the user wants to review a PR visually, generate an HTML/visual diff report, or see PR feedback linked to principles (e.g. an unnecessary useMemo/useCallback) before commenting. Don't use for text-only PR feedback (use code-review), browser UI screenshots (use visual-validate), or orchestrating multiple reviewers (use review).

  • Chanjing credentials guard

    chanjing-ai/chan-skills/skills/chanjing-credentials-guard Skill

    no license19★ repo

    Guide users to configure local Chanjing credentials safely via local commands only, and validate local token status when needed.

  • Chatbot review

    composio-community/support-skills/chatbot-review Skill

    no license19★ repo

    Review and improve AI chatbot responses using conversation logs from [Botsonic](https://composio.dev/toolkits/botsonic), [Docsbot](https://composio.dev/toolkits/docsbot-ai), or [Landbot](https://composio.dev/toolkits/landbot)

  • Email verify

    composio-community/support-skills/email-verify Skill

    no license19★ repo

    Bulk verify customer email addresses using [Clearout](https://composio.dev/toolkits/clearout) or [Mailcheck](https://composio.dev/toolkits/mailcheck)

  • Sentiment check

    composio-community/support-skills/sentiment-check Skill

    no license19★ repo

    Analyze customer message text for sentiment, urgency, and emotional tone.

  • Literature review

    sshtomar/claude-code-skills-social-science/skills/literature-review Skill

    19★ repo

    Systematic literature review methodology for social science research. Use when conducting systematic reviews, research synthesis, meta-analyses, scoping reviews, or comprehensive literature searches across economics, political science, sociology, education, public health, and development. Produces structured notebook cells with search strategy, evidence table, thematic synthesis, and gap analysis.

  • Finishing a development branch

    CodingCossack/agent-skills-library/skills/finishing-a-development-branch Skill

    no license19★ repo

    Git branch completion workflow. Use when implementation is complete, tests pass, and a feature branch needs to be integrated via merge, pull request, or cleanup.

    The same file is in 8 other repositories

  • Receiving code review

    CodingCossack/agent-skills-library/skills/receiving-code-review Skill

    no license19★ repo

    Assesses and responds to incoming code review feedback on PRs (reviewer comments, requested changes), especially when suggestions are unclear, technically questionable, or scope-expanding. Use before implementing review suggestions to align on intent and keep changes minimal.

    The same file is in 8 other repositories

  • Requesting code review

    CodingCossack/agent-skills-library/skills/requesting-code-review Skill

    no license19★ repo

    Use when you need to request a code review for a PR/MR and want a consistent review brief (context, scope, risk areas, test instructions, acceptance criteria) before merge.

    The same file is in 8 other repositories

  • Using git worktrees

    CodingCossack/agent-skills-library/skills/using-git-worktrees Skill

    no license19★ repo

    Git worktree–based workspace isolation for parallel or non-disruptive development. Use when work must occur without modifying or interfering with the current working tree.

    The same file is in 8 other repositories

  • Verification before completion

    CodingCossack/agent-skills-library/skills/verification-before-completion Skill

    no license19★ repo

    Verification discipline for completion claims. Use when about to assert success, claim a fix is complete, report tests passing, or before commits and PRs. Enforces evidence-first workflow.

    The same file is in 8 other repositories

  • Add

    pilotspace/ADD/add-method/skill/add Skill

    19★ repo

    ADD (AI-Driven Development) — a minimal, state-tracked workflow: the AI writes the code, the human owns direction and verification. Drives every feature through one lean PLAN.md: Specify → Plan → Tests & Scenarios → Build → Verify → Observe, red/green TDD built in. Use whenever a repo has `.add/`, or the user says "add", "start a task", "next phase", "specify this feature", "ADD method", "AI-driven development", or wants spec/tests-first discipline over vague-prompt coding. Also resumes work across sessions via `.add/state.json` (never re-read the whole repo).

  • Add

    pilotspace/ADD/add-method/src/add_method/_bundled/skill/add Skill

    19★ repo

    ADD (AI-Driven Development) — a minimal, state-tracked workflow: the AI writes the code, the human owns direction and verification. Drives every feature through one lean PLAN.md: Specify → Plan → Tests & Scenarios → Build → Verify → Observe, red/green TDD built in. Use whenever a repo has `.add/`, or the user says "add", "start a task", "next phase", "specify this feature", "ADD method", "AI-driven development", or wants spec/tests-first discipline over vague-prompt coding. Also resumes work across sessions via `.add/state.json` (never re-read the whole repo).

  • Anti ai

    travsteward/openwriter/skills/anti-ai Skill

    19★ repo

    Anti-AI detection pass for any written text. Hard rules that strip the statistical fingerprints AI writing leaves behind — em-dash density, contrastive formula ("not X, it's Y"), nuclear phrases, copula inflation, sycophantic filler, uniform contractions, colon overuse, register monotony. Two tiers: hard rules (always fix) and voice-gated checks (verify against voice profile if present). Use when: "/anti-ai", "anti-ai pass", "anti-ai check", "strip ai signals", "does this sound like ai", "ai detection check", "humanize this", "remove ai fingerprints".

  • Overcast verify media

    kdr/overcast/skills/overcast-verify-media Skill

    19★ repo

    Is this real? — triage whether an image or video was altered by accumulating independent leads: C2PA / Content Credentials provenance, EXIF capture metadata, ELA/noise forensic overlays, and a sun/shadow time check — never a single-signal call.

  • Adversarial review

    event4u-app/agent-config/dist/agent-src/skills/adversarial-review Skill

    19★ repo

    ONLY on a request for adversarial review, devil's advocate, stress-test, or honest critique ('poke holes', 'be brutal', 'was hältst du davon') — NOT routine code/design review.

  • Agent security review

    event4u-app/agent-config/dist/agent-src/skills/agent-security-review Skill

    19★ repo

    Use for an adversarial red-team / blue-team / auditor review of an AI agent's CONFIG + behaviour (rules, skills, MCP, hooks, permissions) — attack-chain → defensive-gap list, not a code audit.

  • Architecture review lens

    event4u-app/agent-config/dist/agent-src/skills/architecture-review-lens Skill

    19★ repo

    Use when a diff may break system boundaries, dependency direction, or cross-service contracts — fifth judge dispatched by /review-changes alongside the four standard judges.

  • Authz review

    event4u-app/agent-config/dist/agent-src/skills/authz-review Skill

    19★ repo

    Use when reviewing authorization end-to-end — route → gate → policy → query scope → response filter — before changes to permissions, tenants, ownership, or admin flows.

  • Check refs

    event4u-app/agent-config/dist/agent-src/skills/check-refs Skill

    19★ repo

    Use when verifying cross-references between skills, rules, commands, guidelines, and context documents are not broken after edits, renames, or deletions.

  • Code review

    event4u-app/agent-config/dist/agent-src/skills/code-review Skill

    19★ repo

    Use when the user says "review this", "check my code", or wants feedback on changes. Reviews for correctness, quality, security, and coding standards.

  • Contract review

    event4u-app/agent-config/dist/agent-src/skills/contract-review Skill

    19★ repo

    Use when reviewing a contract clause-by-clause from your party's side — buyer/seller/vendor/licensee. Triggers on 'review this contract', 'redline this MSA', 'is this clause a problem'.

  • Conventional commits writing

    event4u-app/agent-config/dist/agent-src/skills/conventional-commits-writing Skill

    19★ repo

    Use when writing commit messages or squash-merge titles — `feat:`, `fix:`, `chore:`, scopes, breaking changes — even when the user just says 'commit this' without naming Conventional Commits.

  • Decision review

    event4u-app/agent-config/dist/agent-src/skills/decision-review Skill

    19★ repo

    Use to audit a past architectural decision — did the chosen option hold up, what assumptions drifted, should the ADR be superseded? Backward review only; does not lock new choices.

  • Design review

    event4u-app/agent-config/dist/agent-src/skills/design-review Skill

    19★ repo

    Use when the user says "review the design", "check the UI", or wants a comprehensive UI/UX review. Uses a 7-phase methodology covering interaction, responsiveness, accessibility, and more.

  • Dpa review

    event4u-app/agent-config/dist/agent-src/skills/dpa-review Skill

    19★ repo

    Use when reviewing a DPA as controller or processor against GDPR Art. 28 — GREEN/YELLOW/RED gap frame, never a final call. Triggers on "review this DPA", "check this DPA".

  • Finishing a development branch

    event4u-app/agent-config/dist/agent-src/skills/finishing-a-development-branch Skill

    19★ repo

    Use when the feature is implementation-complete and the next step is 'ship it' — verifies, cleans up, and routes to merge/PR/park/discard — even when the user just says 'I'm done, what now?'.

  • Git workflow

    event4u-app/agent-config/dist/agent-src/skills/git-workflow Skill

    19★ repo

    Use when working with Git — branch naming, commit messages, PR creation, rebasing, or the code review process — even when the user says 'push this' or 'merge the branch' without naming Git.