agentsclimarketplace

Review & quality

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

  • Scenario branch

    natexai2026/2030-skills/skills/scenario-branch Skill

    0★ repo

    Replace a single point-forecast with 3–5 internally consistent futures built from named driver variables, each with triggering conditions, an ordinal plausibility, and how it propagates to other domains. Use whenever forecasting, planning under uncertainty, stress-testing a strategy, assessing risk, or answering "what will happen with X." Triggers on "what's the outlook for," "where is this heading," "will X happen by year N," roadmap and contingency planning, red-teaming a bet, and any question about the future where a single confident number would be a lie. Especially apt when the honest answer is "it forks."

  • Blender verify

    nubasu/Pseudo-Fable-Framework/frameworks/pseudo-fable-blender/.claude/skills/blender-verify Skill

    0★ repo

    Verification and quality-gate protocol for Blender work — the probe armory (auto-framed 4-view rig, clay pass, wireframe pass, turntable, close-ups, data probes), the critical-reading order, the six-axis rubric with anchored scores per quality tier, the excellence loop (senior-artist critique passes until only cosmetics remain), and the final QA gate mapping every spec criterion to render or probe evidence. Use at every build-loop gate, whenever unsure the model is right, and always before reporting a modeling task done.

  • Finish gate

    nubasu/Pseudo-Fable-Framework/frameworks/pseudo-fable-lift/.claude/skills/finish-gate Skill

    0★ repo

    Mandatory completion gate before reporting any coding task as done — contract coverage with evidence, real end-to-end verification, adversarial diff review, blast-radius check, honest report. If any gate fails, the task is still "in progress". Use immediately before declaring completion; no exceptions.

  • Grill founder

    lightarktech/founder-coding-skills/skills/grill-founder Skill

    0★ repo

    Interview a non-technical founder to surface blind spots before executing any deliverable — code or otherwise. Use before a feature request, a launch, publishing or any external content, marketing copy and positioning decisions, pricing, deploy, hosting, domain or migration work, infrastructure changes, or dispatching agents/subagents to do the building. Trigger on any vague instruction ("add a login page", "refresh the site", "make it feel warmer", "just ship it") and on any request with irreversible side effects or more than an hour of work.

  • Two axis review

    lightarktech/founder-coding-skills/skills/two-axis-review Skill

    0★ repo

    Review finished work on two separate axes — craft quality and faithfulness to what was asked — and never let one axis excuse the other. Use before merging any meaningful change.

  • Code review

    sumitake/agent-collab/plugins/agent-collab/skills/code-review Skill

    no license0★ repo

    Unified dynamic-host agent collaboration policy and signed-runtime client

  • Debate

    sumitake/agent-collab/plugins/agent-collab/skills/debate Skill

    no license0★ repo

    Unified dynamic-host agent collaboration policy and signed-runtime client

  • Governance review

    sumitake/agent-collab/plugins/agent-collab/skills/governance-review Skill

    no license0★ repo

    Unified dynamic-host agent collaboration policy and signed-runtime client

  • Intent check

    sumitake/agent-collab/plugins/agent-collab/skills/intent-check Skill

    no license0★ repo

    Unified dynamic-host agent collaboration policy and signed-runtime client

  • Logic check

    sumitake/agent-collab/plugins/agent-collab/skills/logic-check Skill

    no license0★ repo

    Unified dynamic-host agent collaboration policy and signed-runtime client

  • Merge resolve

    sumitake/agent-collab/plugins/agent-collab/skills/merge-resolve Skill

    no license0★ repo

    Unified dynamic-host agent collaboration policy and signed-runtime client

  • Migration doctor

    sumitake/agent-collab/plugins/agent-collab/skills/migration-doctor Skill

    no license0★ repo

    Unified dynamic-host agent collaboration policy and signed-runtime client

  • Qa verify

    sumitake/agent-collab/plugins/agent-collab/skills/qa-verify Skill

    no license0★ repo

    Unified dynamic-host agent collaboration policy and signed-runtime client

  • Red team

    sumitake/agent-collab/plugins/agent-collab/skills/red-team Skill

    no license0★ repo

    Unified dynamic-host agent collaboration policy and signed-runtime client

  • Second opinion

    sumitake/agent-collab/plugins/agent-collab/skills/second-opinion Skill

    no license0★ repo

    Unified dynamic-host agent collaboration policy and signed-runtime client

  • Simulate user

    sumitake/agent-collab/plugins/agent-collab/skills/simulate-user Skill

    no license0★ repo

    Unified dynamic-host agent collaboration policy and signed-runtime client

  • Visual review

    sumitake/agent-collab/plugins/agent-collab/skills/visual-review Skill

    no license0★ repo

    Review a screenshot, mockup, slide, chart, diagram, photograph, or marketing asset for hierarchy, readability, density, consistency, accessibility, and brand fit. Use when the user says "review this design," "look at this screenshot," "design feedback," "accessibility review," "is this on-brand," or "compare these variants," or when a visual artifact is about to ship. The unified plugin currently has no managed cross-family image transport, so this skill provides an honest primary-only visual pass or reports independent visual review unavailable; it never fabricates a verifier call.

  • Opsec review

    fevra-dev/Subrosa/skills/opsec-review Skill

    0★ repo

    Red-teams documents, code, READMEs, social posts, commit messages, and paste content for inadvertent operational security leakage before external exposure. Use when user says "review this before I post", "OPSEC check", "is this safe to share", "audit this README", "pre-flight check", "what does this reveal", "check before I push", or when preparing any artifact for public release, GitHub push, social media, client delivery, or external API submission. Distinct from PII redaction — focuses on what an adversary can INFER from context, metadata, structure, and timing signals, not just explicit identifiers.

  • Robots txt validator

    vistabylara-dev/vista-claude-skills/skills/robots-txt-validator Skill

    0★ repo

    Free Claude Skills for AI developers, Shopify experts, marketers, and businesses. Built by Vista by Lara.

  • Alterlab cdm film analysis

    prone-dc302/AlterLab-FC-Skills/skills/cdm/alterlab-cdm-film-analysis Skill

    0★ repo

    This skill should be used when the user asks about "film analysis", "movie analysis", "film essay", "sequence analysis", "mise-en-scene", "film theory", "cinematography analysis", "film critique", "act as a film analyst", "film analysis mode", "formal analysis", "auteur theory", "film semiotics", "narrative analysis film", "film studies essay", "film review vs analysis", "close reading film", "shot-by-shot analysis", "annotated film bibliography", "film criticism", or needs expertise in academic film analysis, theory application, formal cinematic analysis, and film essay writing. Part of the AlterLab FC Skills collection (Cinema & Digital Media department).

    The same file is in 1 other repository

  • Alterlab rma literature reviewer

    prone-dc302/AlterLab-FC-Skills/skills/rma/alterlab-rma-literature-reviewer Skill

    0★ repo

    This skill should be used when the user asks about "literature review", "systematic review", "source evaluation", "annotated bibliography", "literature mapping", "research gap", "database searching", "Google Scholar", "JSTOR", "Scopus", "Web of Science", "act as a literature reviewer", "literature reviewer mode", "finding sources", "academic sources", "peer-reviewed articles", "citation management", "reference list", "literature search strategy", "inclusion criteria", "exclusion criteria", "PRISMA", "thematic analysis of literature", "source credibility", "research synthesis", "scoping review", "narrative review", "meta-analysis planning", "literature matrix", or needs expertise in finding, evaluating, organizing, and synthesizing academic literature. Part of the AlterLab FC Skills collection (Research Methods & Academic Writing department).

    The same file is in 1 other repository

  • Alterlab vcd design critic

    prone-dc302/AlterLab-FC-Skills/skills/vcd/alterlab-vcd-design-critic Skill

    0★ repo

    This skill should be used when the user asks about "design critique", "design review", "portfolio review", "visual analysis", "design writing", "design criticism", "formal analysis", "semiotic analysis", "design history", "design essay", "act as a design critic", "design critic mode", "critique my design", "review my portfolio", "design feedback", "visual rhetoric", "design theory", "composition analysis", "typography critique", "layout analysis", "design principles evaluation", "Gestalt analysis", "design case study", "design presentation", "design rationale", "defend design decisions", or needs expertise in design critique, portfolio review, visual analysis, and design writing. Part of the AlterLab FC Skills collection (VCD department).

    The same file is in 1 other repository

  • Grill

    supermodo/skills/skills/grill Skill

    0★ repo

    Twin-agent adversarial interview that locks a task or design before implementation. Two models plan independently, attack each other's plans, and only genuinely user-owned questions reach you — the locked outcome is handed to librarian to write. Use for 'grill', 'grill me', plan stress-test, design interview, new-task intake, spec lock, or a flow `needs-input` escalation.

  • Release

    supermodo/skills/skills/release Skill

    0★ repo

    Run a versioned release with git-flow discipline: deterministic preflight (branch, clean tree, Conventional Commits since last tag → suggested semver bump), changelog entry written from fragments/commits into the changelog file automatically, then the exact squash-merge/tag/push/GitHub-release sequence printed and consent-gated by default (configurable auto mode). Two configurable modes: light (dev → main) and full git-flow (release/* stabilization + hotfix/* branches). Use for 'release', 'cut a release', 'ship a version', 'bump the version', 'publish vX.Y.Z', 'hotfix production' — whenever accumulated work should become a tagged, published version.

  • Tests

    supermodo/skills/skills/tests Skill

    0★ repo

    Fixes failing tests and lint/type errors, audits test-suite quality with a fleet of specialist reviewers, or drives coverage — for any project configured with a supermodo skills.config.json. Modes: `tests` (default) fixes every failure tier by tier (unit, integration, E2E, lint); `tests audit [scope]` spawns parallel specialist reviewers (spec-alignment, assertion-strength, corner-cases, coverage-balance, and a domain lens derived from the project's docs), runs mutation probes where configured, and adversarially verifies every finding with a second model before reporting; `tests coverage` drives coverage to the configured target with a balance check. Use whenever the user mentions failing tests, lint errors, "make tests pass", green build, flaky tests, test quality, weak or missing tests, corner cases, coverage, mutation testing, or asks whether the tests actually protect the core logic — even without "/tests".

  • Ux reviewer

    tamasbege/staff-engineer-skills/plugins/staff-engineer-skills/skills/ux-reviewer Skill

    0★ repo

    Adversarial, persona-driven usability review of an existing UI or flow — a live URL, screenshots, a Figma link, or a described user flow — reviewed through four user archetypes plus Nielsen's usability heuristics to surface friction, confusion, and accessibility gaps before they ship. Use when reviewing a design or flow before dev handoff, auditing a shipped screen for usability problems, or asked to "review the UX," "critique this flow," or "find usability issues." This is a critique gate against a design that already exists — not generative user research (personas or journey maps built from real user data), which is discovery work outside this skill's scope.

  • Follow the thread

    serhiy-bzhezytskyy/contrib-receipts/skills/follow-the-thread Skill

    0★ repo

    When a red CI test, a failing check, or a single bug crosses your path, follow it instead of dismissing it — one thread reliably sources many issues worth working. A failing test maps to an existing issue whose root cause is often an existing UPSTREAM bug (downstream symptom → upstream cause); fixing that bug means reading the surrounding subsystem, where adjacent open issues surface; searching near the one you're fixing (same area / same reporter) seeds the next. A convenient "it also fixes X" is a hypothesis, not a finding — verify the mechanism. This is a SOURCING method: it finds where the help actually is, before any PR. Use when you hit a red CI on your own PR, a flake, or one bug and want to find the real work around it. Trigger terms: red CI, flaky test, follow the thread, downstream symptom, upstream root cause, adjacent issue, sibling bug, "not my bug", where's the real work.

  • Match the house shape

    serhiy-bzhezytskyy/contrib-receipts/skills/match-the-house-shape Skill

    0★ repo

    Before shaping a PR, mine what ACTUALLY merges in this house — the median churn, changed-file count, title convention, and test-touch rate of recently merged PRs — and size/shape your contribution to that median. A reviewer's implicit expectation is set by what they routinely merge, not by what CONTRIBUTING.md states; a PR in the house's usual shape is cheaper to review and so more likely to land as help. Measured on Apache Solr: 3,510 merged PRs settle on a clear median shape (churn 58, 4 changed files, 67.6% JIRA-key titles, 4.0 d to merge). Use before opening a PR, after picking the work. Trigger terms: house shape, median PR size, right-size the PR, split the PR, title convention, what actually merges.

  • No force push a reviewed pr

    serhiy-bzhezytskyy/contrib-receipts/skills/no-force-push-a-reviewed-pr Skill

    0★ repo

    On a PR that already has reviewers, push follow-up changes as plain new commits only — never `git commit --amend`, never `git push --force` / `--force-with-lease`. Force-push rewrites the commits reviewers' inline comments anchor to, resets the GitHub review state, and forces a cold re-read — the opposite of the incremental trust you are building. Use whenever you push any change to a PR someone has already looked at. Trigger terms: force-push, --amend, --force-with-lease, rebase, "clean up history", pushing to an under-review PR.

  • Sign off the house way

    serhiy-bzhezytskyy/contrib-receipts/skills/sign-off-the-house-way Skill

    0★ repo

    Before opening a PR, know which contributor sign-off THAT house requires and make sure it's present — the contracts differ by house and a missing one is an instant, automated "didn't read the rules" bounce. Eclipse projects (e.g. Jetty) gate every PR on an ECA plus a DCO `Signed-off-by` trailer on each commit; Apache projects (Solr/Lucene) use a CLA with the committer resolving on merge and need no per-commit trailer; other houses need neither. Check the house's contract first, not after a bot rejects you. Use at front-gate, before the first commit. Trigger terms: DCO, ECA, CLA, Signed-off-by, sign-off, `git commit -s`, eca check, contributor agreement.

  • Track whose court

    serhiy-bzhezytskyy/contrib-receipts/skills/track-whose-court Skill

    0★ repo

    To answer "is anything waiting on me?", run a channel-complete status check across EVERY channel a maintainer can reach you on — GitHub PR issue-comments, GitHub inline review-comments, GitHub reviews, watched-issue comments, ASF JIRA, and the dev@ mailing list — plus git diffs as a seventh source. Compare the last HUMAN commenter (filtering commit-bot authors) to you to decide whose turn it is. Hand-checking one channel silently misses the others. Use on any "check status" / "whose turn" / "anything waiting on me" request. Trigger terms: check status, whose court, turn tracking, ball on me, follow-up, did they reply, nudge vs wait.

  • Verify before a committer comment

    serhiy-bzhezytskyy/contrib-receipts/skills/verify-before-a-committer-comment Skill

    0★ repo

    Before asserting a technical claim in a public JIRA/PR/committer-facing comment — "PR X fixes Y", "the bug is in layer Z", "test T still fails", "commit C did D" — verify it by reading the actual code path and running the test on clean state. Do NOT infer from PR titles, commit messages, or the issue link-graph. State your confidence (verified / inferred / open). A confident-wrong claim to a committer, especially about your OWN PR's scope, costs trust fast. Use before any committer-facing technical assertion. Trigger terms: post a comment, "this fixes", root cause, which layer, still fails, commit did X, assumed or checked.

  • Create pr

    YasuakiOmokawa/skills/plugins/create-pr/skills/create-pr Skill

    0★ repo

    Creates a Conventional-Commits PR (draft by default; ready for review when the user explicitly requests it) from the current branch with generated title, body, labels, and milestone, without confirmation. Use when the user says "PR を作って" / "draft PR" / "PR 作成して" / "ready for review で PR を作って", optionally with `[base-branch]` and per-section detail-expansion instructions (e.g. "設計判断は詳しく") as arguments.

  • Mece plan review

    YasuakiOmokawa/skills/plugins/mece-plan-review/skills/mece-plan-review Skill

    0★ repo

    Verifies acceptance criteria for MECE coverage with spec (BB) and code (WB) perspectives — run inline by the main agent by default, with a fresh red-team judge dispatched only when critical candidates emerge; risk domains (auth/billing/payment/migration) or >15 AC escalate to deep tier (parallel BB/WB subagents + mandatory red team), and the Devin wiki researcher joins only on explicit user opt-in. Records coverage gaps and duplicates in the analysis file. Use when AC is already defined in the analysis file via /define-acceptance-criteria and MECE verification is required before implementation, or when the user says "AC の網羅性を検証して" / "MECE 検証して". Not typically invoked during PoC / throwaway-validation phases (the assumption ledger substitutes there).

  • Polish before commit

    YasuakiOmokawa/skills/plugins/polish-before-commit/skills/polish-before-commit Skill

    0★ repo

    Auto-fixes convention and pattern-consistency issues, runs lint, and aggregates remaining judgment calls before stopping for the user (or, when explicitly delegated in orchestrated mode, escalating to a ledger and returning instead of waiting). Ingests leftover findings from the built-in `/code-review` skill run by the user just before this skill (this skill never invokes `/code-review` itself — its disable-model-invocation setting rejects Skill-tool launches). Use when finalizing a branch, just before `git commit` or `/create-pr`, when reviewing someone else's PR without editing files (review-only mode), or whenever the user says "仕上げて" / "polish" / "コミット前チェック" / "レビューのみで見て".

  • Review code quality

    YasuakiOmokawa/skills/plugins/review-code-quality/skills/review-code-quality Skill

    0★ repo

    Use when finishing self-review of an implementation, before requesting PR review, when inspecting someone else's PR or a PR not checked out locally (PR review mode), when a diff updates a domain model attribute (`plan_code` / `role` / `status` 等), or when the user says "コード品質をレビューして" / "品質レビュー". Analyzes the diff across cohesion and coupling (plus business-impact for domain-attribute changes — Ruby/Rails diffs only, skipped when the diff has no .rb/.rake files) and hands off every 🔴/🟠 finding to /polish-before-commit as needs-judgment without editing files. Readability-level fixes (minor renames, simplification, efficiency) are covered by the built-in /code-review skill, not this plugin.

  • Review design

    YasuakiOmokawa/skills/plugins/review-design/skills/review-design Skill

    0★ repo

    Agent skills for improve AI driven development

  • Review plan diff

    YasuakiOmokawa/skills/plugins/review-plan-diff/skills/review-plan-diff Skill

    0★ repo

    実装完了後に、確定プラン (finalize-plan 出力)、または DD 該当タスクを転記した簡易プランと実装後の diff を突き合わせ、実装漏れ・仕様逸脱・計画外差異を検出したいときに使用する。「プランと突き合わせて」「実装漏れがないか見て」「diffがプラン通りか確認して」等の依頼で起動する。

  • Idea validation autopilot

    nbsp1221/agent-skills/skills/idea-validation-autopilot Skill

    no license0★ repo

    Use when a founder has a rough product idea and wants autonomous deep validation, market and competitor research, and an evidence-based MVP decision with minimal back-and-forth.

  • Create pull request

    theinterneti/TTA.dev/.claude/skills/create-pull-request Skill

    0★ repo

    Use this skill when creating or updating a pull request in the TTA.dev repository. Covers PR structure, review expectations, and checklist.

  • Git commit

    theinterneti/TTA.dev/.claude/skills/git-commit Skill

    0★ repo

    Use this skill when making git commits in the TTA.dev repository. Enforces Conventional Commits format and pre-commit quality checks.

  • Self review checklist

    theinterneti/TTA.dev/.claude/skills/self-review-checklist Skill

    0★ repo

    Use this skill before submitting code for review or merging a pull request. Covers a pre-merge checklist of common mistakes to catch.

  • Build test verify

    theinterneti/TTA.dev/.github/skills/build-test-verify Skill

    0★ repo

    Use this skill when asked to build the project, run tests, lint the code, check types, or verify that the TTA.dev platform is stable before committing. Invoke when the user says "run tests", "check quality", "lint", "format", "verify", or before any commit or PR.

  • Core conventions

    theinterneti/TTA.dev/.github/skills/core-conventions Skill

    0★ repo

    Use this skill when writing or reviewing Python code in TTA.dev. Covers the package manager (uv), type hint standards, primitives usage, anti-patterns to avoid, state management, and LLM provider strategy. Invoke when the user says "write code", "review code", "add a feature", or asks about conventions or standards.

  • Create pull request

    theinterneti/TTA.dev/.github/skills/create-pull-request Skill

    0★ repo

    Use this skill when creating or updating a pull request in the TTA.dev repository. Covers PR title format, description template, review expectations, and pre-submit checklist. Invoke when the user says "create a PR", "open a pull request", "submit my changes", or "make a PR".

  • Git commit

    theinterneti/TTA.dev/.github/skills/git-commit Skill

    0★ repo

    Use this skill when making git commits in the TTA.dev repository. Enforces Conventional Commits format and pre-commit quality checks. Invoke when the user says "commit", "git commit", "save changes", "commit my work", or asks how to commit code.

  • Self review checklist

    theinterneti/TTA.dev/.github/skills/self-review-checklist Skill

    0★ repo

    Use this skill before submitting code for review or merging a pull request. Covers a pre-merge checklist of common mistakes to catch across code quality, testing, security, and documentation. Invoke when the user says "review my code", "pre-merge check", "self-review", "am I ready to submit", or before opening a PR.

  • Greenfield monorepo

    gabriel-f-santos/coding-agents/skills/greenfield-monorepo Skill

    no license0★ repo

    Bootstrap a brand-new polyglot monorepo from zero — interview for the apps and stacks, then scaffold a runnable hello-world per app with current best-practice harness, lint, tests, pre-commit, Docker Compose dev stack with seed data, dev scripts (up/down/restart/seed), root + per-app AGENTS.md, and CI. Use when the user wants to "start a new project/monorepo", "scaffold a greenfield repo", "set up frontend + backend + mobile", "iniciar um projeto do zero", "criar o monorepo", "montar o esqueleto", "configurar lint/test/pre-commit/docker do projeto novo", or hands over an architecture.md to build from. Ships two pinned stacks (Vite+React→Cloudflare Workers, FastAPI async) and a generic research-and-scaffold path (context7/web) for any other stack (LangGraph, Go realtime, Flutter, …). Do not use to add a feature to an existing app, to write a single Dockerfile/CI file in isolation, or to design product/architecture from scratch (chain to product-brainstorming / tech-discovery for that).

  • Review functionality

    gabriel-f-santos/coding-agents/skills/review-functionality Skill

    no license0★ repo

    Review implemented code for conformance to a phase/feature contract and for correctness bugs. Use to check that what was built actually meets its acceptance criteria — "revisa se a feature faz o que devia", "conformance review", "review against the spec", "achou bug na fase?". Reads the phase contract (acceptance criteria, deliverables) + the diff and reports, confidence-based, whether each criterion is met and any correctness defects (logic, edge cases, error paths, concurrency). Read-only — reports findings, does not fix. Designed to run standalone or as a subagent of review-phase. Do not use for security (review-security) or style/cleanup (review-quality).

  • Review phase

    gabriel-f-santos/coding-agents/skills/review-phase Skill

    no license0★ repo

    Review a just-implemented phase/feature across functionality, security, and quality by fanning out three reviewers as subagents, scoped to the phase contract. Use after building something — "revisa a fase", "review phase X", "code review da feature", "revisa o que foi implementado", "revisão da phase-NN". Reads docs/phases/phase-NN-<slug>.md (acceptance criteria, deliverables) + the diff, runs review-functionality, review-security and review-quality (parallel subagents when available), de-dupes and prioritizes findings P0/P1/P2, prints a summary to screen and writes the full report to a gitignored artifacts path. Do not use for live UI/runtime smoke (use e2e-test-review) or to apply fixes (use simplify/refactor).

  • Review quality

    gabriel-f-santos/coding-agents/skills/review-quality Skill

    no license0★ repo

    Review changed code for "crap" reduction — reuse, simplification, efficiency, dead code, duplication, naming, and altitude. Use to clean up what was just built — "reduz a gambiarra", "revisa qualidade do código", "tem duplicação/dead code?", "dá pra simplificar essa feature?". Reports findings only (does not apply fixes — use simplify/refactor for that), confidence-based, never security or correctness (those are review-security / review-functionality). Runs standalone or as a subagent of review-phase.

  • Review security

    gabriel-f-santos/coding-agents/skills/review-security Skill

    no license0★ repo

    Security review of changed code, scoped to a phase/feature diff. Use to find exploitable vulnerabilities in what was just built — "revisa segurança da fase", "tem vuln nessa feature?", "security review do diff", "checa injection/authz/IDOR". Reports HIGH-confidence, attacker-reachable issues only (injection, broken authZ / cross-tenant / IDOR, secret exposure, missing validation, SSRF, deserialization, crypto misuse) AND supply-chain gaps (unpinned deps / uncommitted lockfile / no cooldown). Read-only — reports, does not fix. Runs standalone or as a subagent of review-phase. Do not use for functional conformance (review-functionality) or style/cleanup (review-quality).

  • Audit design review

    magallon/website-audit-toolkit/audit-design-review Skill

    0★ repo

    Visual design audit for static B2B marketing sites on cPanel. Verifies that the design meets production craft standards before launch. Reviews design system integrity (CSS token architecture, spacing system, depth strategy, border radius scale, typography system), visual craft through four diagnostic tests (swap test, squint test, signature test, token test), component and interaction states (interactive element states, data-dependent states, surface elevation, typography hierarchy), and design system documentation for consistent screen generation. Includes anti-pattern detection checklist. Run as the tenth and final audit in the pre-production protocol.

  • Verification before completion

    karim-bhalwani/agent-skills-collection/skills/verification-before-completion Skill

    0★ repo

    Use when about to claim work is complete, fixed, or passing—requires running verification commands and confirming output before making any success claims.

  • Interswitch transfers

    rexedge/interswitch/skills/interswitch-transfers Skill

    no license0★ repo

    Interswitch Transfers API — validate bank accounts, initiate single and bulk fund transfers, check transfer status, and resolve bank codes. Use this skill whenever building payout flows, processing disbursements, validating bank accounts before transfer, generating MAC hashes for transfer security, or implementing bulk transfer operations. Also use when you see references to /api/v2/quickteller/payments/transfers, account validation, MAC hash, sender/beneficiary objects, or bank code resolution.

  • Pull request writer

    WasDavidOliveira/irracional-skills/pull-request-writer Skill

    no license0★ repo

    Use when asked to write or review pull request descriptions, PR summaries, release notes from a PR, or changelog text based on a code diff, ensuring mandatory sections are complete, testable, and reviewer-friendly.

  • Finishing a development branch

    songsunny00/MySkills/CoderSkills/.agents/skills/finishing-a-development-branch Skill

    no license0★ 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 17 other repositories

  • Receiving code review

    songsunny00/MySkills/CoderSkills/.agents/skills/receiving-code-review Skill

    no license0★ 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 28 other repositories

  • Requesting code review

    songsunny00/MySkills/CoderSkills/.agents/skills/requesting-code-review Skill

    no license0★ repo

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

    The same file is in 3 other repositories

  • Review prd

    songsunny00/MySkills/CoderSkills/.agents/skills/review-prd Skill

    no license0★ repo

    以开发视角审查产品需求文档,识别需求不清晰、交互场景遗漏、逻辑冲突、异常处理缺失等问题,输出结构化 Excel 报告