agentsclimarketplace

Test

10,621 rows, by stacks then stars

1,559 of these skill files have been read, by 1,201 distinct authors, and what they tell an agent counted. What Test authors agree on, and what they forbid

  • E2e playwright

    lennney/gate-all-skills/skills/website/e2e-playwright Skill

    no license1★ repo

    End-to-end testing with Playwright in Next.js applications — user flow coverage, component testing, and CI integration. Use when writing E2E tests, debugging flaky tests, or setting up test infrastructure.

  • Gate testcov

    lennney/gate-all-skills/skills/workflow/gate-testcov Skill

    no license1★ repo

    测试覆盖 / Test coverage. Adds tests for core functionality. Use when the user wants to add test coverage to their project.

  • Test gen zh

    YuAICode/ai-skills/skills/test-gen-zh Skill

    1★ repo

    给指定函数或文件生成测试,配合 TDD 习惯。当用户说"帮我生成测试 / 给这个函数写测试 / test-gen-zh / 帮我补测试用例"时触发。bin 探测测试框架,Claude 读实现并按框架惯例生成覆盖正常/边界/错误路径的测试。

  • Visual review

    zeikar/dotfiles/claude/.claude/skills/visual-review Skill

    1★ repo

    This skill should be used after UI-affecting changes to visually verify rendering — when the user asks to "visually check", "review how it looks", "see how the screen looks", "check the UI", or after building/modifying components, modals, layout, responsive, or dark-mode behavior. Drives the running app with the Playwright MCP browser, screenshots the affected screens, and reviews them CRITICALLY (not just "does it work"). Agent-driven review, NOT committed visual-regression tests. Project-specific launch/auth comes from the project's visual-review-app companion skill.

  • Odoo test runner

    assoumaaa/odoo-superpowers/skills/odoo-test-runner Skill

    no license1★ repo

    Use when verifying an Odoo development before claiming "it works," or when writing the tests themselves. Spins up a fresh DB, installs the module, and proves the feature behaves as the ticket asked via `--test-enable`, the shell, or the UI — and carries the conventions for the tests: class choice, `@tagged`, `assertRecordValues`, the demo-user password trap, tours. Invoke whenever tempted to say "it works" without proving it on a clean install, or before adding files under tests/.

    The same file is in 1 other repository

  • Vitest

    DigitalPine/claude-skills/plugins/vitest/skills/vitest Skill

    1★ repo

    Setup, configure, audit, and modernize Vitest testing in projects. Use when creating new test configs, auditing existing Vitest implementations for v4.0+ best practices, fixing deprecated patterns, migrating from Jest, or configuring test environments (Node.js, browser, monorepo). Checks for breaking changes, outdated configs, missing coverage settings, and performance issues. Covers browser mode, visual regression testing, and CI integration.

  • Shaktra tdd

    im-shashanks/claude-plugins/shaktra/skills/shaktra-tdd Skill

    no license1★ repo

    TDD knowledge base — testing practices, coding practices, and implementation patterns. Loaded by SDM workflow agents (sw-engineer, test-agent, developer) for behavioral testing guidance and production-grade coding standards.

  • Design codebase

    Chrike/coding-agent-skills/skills/design-codebase Skill

    no license1★ repo

    Use when the user asks to make or compare a codebase architecture decision involving module boundaries, ownership, interfaces, seams, adapters, domain language, or a throwaway prototype that answers a design question. Also use during implementation only when a non-obvious architecture, ownership, interface, or dependency-boundary decision blocks the next safe edit; a testability concern qualifies only when it demonstrates that kind of boundary pressure. Do not use for ordinary code explanation, straightforward implementation, general test design, flaky tests, mocks, regression coverage, or implementation of an already selected design.

  • Test strategy

    Chrike/coding-agent-skills/skills/test-strategy Skill

    no license1★ repo

    Use when the primary problem is test design, explicit TDD, test-first or red-green-refactor work, test seams, regression coverage, mocks, assertions, fixtures, or timing and wait strategy, or when a requested change needs a non-obvious test level, seam, regression signal, or acceptance proof. Do not use for generic testing explanations, ordinary implementation, unresolved root-cause diagnosis, unresolved architecture or ownership/interface/dependency-boundary decisions, explicit review or feedback handling, or completed-work readiness review.

  • Plan eng review

    Yesterday-AI/ytstack/skills/plan-eng-review Skill

    1★ repo

    Review execution approach for feasibility, architecture, data flow, edge cases, test coverage, performance, and security risks. Auto-detects mode: concept-mode reviews a pitch (OFFICE-HOURS.md) for technical feasibility before any scaffolding; milestone-mode reviews slice-plans (M###-S##-PLAN.md) before plan-task. Use concept-mode optionally after plan-ceo-review to sanity-check the pitched approach; use milestone-mode after slice-milestone to lock architecture before implementation. Thin ytstack wrapper around the vendored gstack plan-eng-review procedure.

  • Test driven development

    Yesterday-AI/ytstack/skills/test-driven-development Skill

    1★ repo

    RED-GREEN-REFACTOR: write a failing test, watch it fail, write minimal code, watch it pass, commit. Thin ytstack wrapper around the vendored superpowers test-driven-development procedure, injecting the current task's plan as context. Use during task execution.

  • Gstack

    Yesterday-AI/ytstack/vendor/gstack Skill

    1★ repo

    Fast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)

  • Browse

    Yesterday-AI/ytstack/vendor/gstack/browse Skill

    1★ repo

    Fast headless browser for QA testing and site dogfooding. Navigate any URL, interact with elements, verify page state, diff before/after actions, take annotated screenshots, check responsive layouts, test forms and uploads, handle dialogs, and assert element states. ~100ms per command. Use when you need to test a feature, verify a deployment, dogfood a user flow, or file a bug with evidence. Use when asked to "open in browser", "test the site", "take a screenshot", or "dogfood this". (gstack)

  • Plan eng review

    Yesterday-AI/ytstack/vendor/gstack/plan-eng-review Skill

    1★ repo

    Eng manager-mode plan review. Lock in the execution plan — architecture, data flow, diagrams, edge cases, test coverage, performance. Walks through issues interactively with opinionated recommendations. Use when asked to "review the architecture", "engineering review", or "lock in the plan". Proactively suggest when the user has a plan or design doc and is about to start coding — to catch architecture issues before implementation. (gstack) Voice triggers (speech-to-text aliases): "tech review", "technical review", "plan engineering review".

  • Qa only

    Yesterday-AI/ytstack/vendor/gstack/qa-only Skill

    1★ repo

    Report-only QA testing. Systematically tests a web application and produces a structured report with health score, screenshots, and repro steps — but never fixes anything. Use when asked to "just report bugs", "qa report only", or "test but don't fix". For the full test-fix-verify loop, use /qa instead. Proactively suggest when the user wants a bug report without any code changes. (gstack) Voice triggers (speech-to-text aliases): "bug report", "just check for bugs".

  • Qa

    Yesterday-AI/ytstack/vendor/gstack/qa Skill

    1★ repo

    Systematically QA test a web application and fix bugs found. Runs QA testing, then iteratively fixes bugs in source code, committing each fix atomically and re-verifying. Use when asked to "qa", "QA", "test this site", "find bugs", "test and fix", or "fix what's broken". Proactively suggest when the user says a feature is ready for testing or asks "does this work?". Three tiers: Quick (critical/high only), Standard (+ medium), Exhaustive (+ cosmetic). Produces before/after health scores, fix evidence, and a ship-readiness summary. For report-only mode, use /qa-only. (gstack) Voice triggers (speech-to-text aliases): "quality check", "test the app", "run QA".

  • Test driven development

    Yesterday-AI/ytstack/vendor/superpowers/skills/test-driven-development Skill

    1★ repo

    Use when implementing any feature or bugfix, before writing implementation code

    The same file is in 33 other repositories

  • Swing review

    SURFLIN2030/swing-skills/skills/swing-review Skill

    1★ repo

    Devil's Advocate stress-testing for code, architecture, PRs, and decisions. Surfaces hidden flaws through structured adversarial analysis with metacognitive depth. Use for high-stakes review, stress-testing choices, or when the user wants problems found deliberately. NOT for routine code review (use engineering:code-review). Triggers on "스트레스 테스트", "stress test", "devil's advocate", "반론", "이거 괜찮아", "문제 없을까", "깊은 리뷰", "critical review", "adversarial".

  • Stress test

    timdevai/proteus/skills/community/from-alireza/c-level-advisor/executive-mentor/skills/stress-test Skill

    1★ repo

    /em -stress-test — Business Assumption Stress Testing

    The same file is in 2 other repositories

  • Browserstack

    timdevai/proteus/skills/community/from-alireza/engineering-team/playwright-pro/skills/browserstack Skill

    1★ repo

    Run tests on BrowserStack. Use when user mentions "browserstack", "cross-browser", "cloud testing", "browser matrix", "test on safari", "test on firefox", or "browser compatibility".

    The same file is in 6 other repositories

  • Coverage

    timdevai/proteus/skills/community/from-alireza/engineering-team/playwright-pro/skills/coverage Skill

    1★ repo

    Analyze test coverage gaps. Use when user says "test coverage", "what's not tested", "coverage gaps", "missing tests", "coverage report", or "what needs testing".

    The same file is in 6 other repositories

  • Fix

    timdevai/proteus/skills/community/from-alireza/engineering-team/playwright-pro/skills/fix Skill

    1★ repo

    Fix failing or flaky Playwright tests. Use when user says "fix test", "flaky test", "test failing", "debug test", "test broken", "test passes sometimes", or "intermittent failure".

    The same file is in 5 other repositories

  • Generate

    timdevai/proteus/skills/community/from-alireza/engineering-team/playwright-pro/skills/generate Skill

    1★ repo

    Generate Playwright tests. Use when user says "write tests", "generate tests", "add tests for", "test this component", "e2e test", "create test for", "test this page", or "test this feature".

    The same file is in 2 other repositories

  • Init

    timdevai/proteus/skills/community/from-alireza/engineering-team/playwright-pro/skills/init Skill

    1★ repo

    Set up Playwright in a project. Use when user says "set up playwright", "add e2e tests", "configure playwright", "testing setup", "init playwright", or "add test infrastructure".

    The same file is in 4 other repositories

  • Migrate

    timdevai/proteus/skills/community/from-alireza/engineering-team/playwright-pro/skills/migrate Skill

    1★ repo

    Migrate from Cypress or Selenium to Playwright. Use when user mentions "cypress", "selenium", "migrate tests", "convert tests", "switch to playwright", "move from cypress", or "replace selenium".

    The same file is in 6 other repositories

  • Pw

    timdevai/proteus/skills/community/from-alireza/engineering-team/playwright-pro/skills/pw Skill

    1★ repo

    Production-grade Playwright testing toolkit. Use when the user mentions Playwright tests, end-to-end testing, browser automation, fixing flaky tests, test migration, CI/CD testing, or test suites. Generate tests, fix flaky failures, migrate from Cypress/Selenium, sync with TestRail, run on BrowserStack. 55 templates, 3 agents, smart reporting.

    The same file is in 5 other repositories

  • Report

    timdevai/proteus/skills/community/from-alireza/engineering-team/playwright-pro/skills/report Skill

    1★ repo

    Generate test report. Use when user says "test report", "results summary", "test status", "show results", "test dashboard", or "how did tests go".

    The same file is in 6 other repositories

  • Review

    timdevai/proteus/skills/community/from-alireza/engineering-team/playwright-pro/skills/review Skill

    1★ 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".

    The same file is in 4 other repositories

  • Testrail

    timdevai/proteus/skills/community/from-alireza/engineering-team/playwright-pro/skills/testrail Skill

    1★ repo

    Sync tests with TestRail. Use when user mentions "testrail", "test management", "test cases", "test run", "sync test cases", "push results to testrail", or "import from testrail".

    The same file is in 6 other repositories

  • Security pen testing

    timdevai/proteus/skills/community/from-alireza/engineering-team/skills/security-pen-testing Skill

    1★ repo

    Use when the user asks to perform security audits, penetration testing, vulnerability scanning, OWASP Top 10 checks, or offensive security assessments. Covers static analysis, dependency scanning, secret detection, API security testing, and pen test report generation.

    The same file is in 1 other repository

  • Senior data scientist

    timdevai/proteus/skills/community/from-alireza/engineering-team/skills/senior-data-scientist Skill

    1★ repo

    World-class senior data scientist skill specialising in statistical modeling, experiment design, causal inference, and predictive analytics. Covers A/B testing (sample sizing, two-proportion z-tests, Bonferroni correction), difference-in-differences, feature engineering pipelines (Scikit-learn, XGBoost), cross-validated model evaluation (AUC-ROC, AUC-PR, SHAP), and MLflow experiment tracking — using Python (NumPy, Pandas, Scikit-learn), R, and SQL. Use when designing or analysing controlled experiments, building and evaluating classification or regression models, performing causal analysis on observational data, engineering features for structured tabular datasets, or translating statistical findings into data-driven business decisions.

    The same file is in 2 other repositories

  • Senior qa

    timdevai/proteus/skills/community/from-alireza/engineering-team/skills/senior-qa Skill

    1★ repo

    Generates unit tests, integration tests, and E2E tests for React/Next.js applications. Scans components to create Jest + React Testing Library test stubs, analyzes Istanbul/LCOV coverage reports to surface gaps, scaffolds Playwright test files from Next.js routes, mocks API calls with MSW, creates test fixtures, and configures test runners. Use when the user asks to "generate tests", "write unit tests", "analyze test coverage", "scaffold E2E tests", "set up Playwright", "configure Jest", "implement testing patterns", or "improve test quality".

    The same file is in 2 other repositories

  • Tdd guide

    timdevai/proteus/skills/community/from-alireza/engineering-team/skills/tdd-guide Skill

    1★ repo

    Test-driven development skill for writing unit tests, generating test fixtures and mocks, analyzing coverage gaps, and guiding red-green-refactor workflows across Jest, Pytest, JUnit, Vitest, and Mocha. Use when the user asks to write tests, improve test coverage, practice TDD, generate mocks or stubs, or mentions testing frameworks like Jest, pytest, or JUnit.

    The same file is in 4 other repositories

  • Helm chart builder

    timdevai/proteus/skills/community/from-alireza/engineering/helm-chart-builder/skills/helm-chart-builder Skill

    1★ repo

    Helm chart development agent skill and plugin for Claude Code, Codex, Gemini CLI, Cursor, OpenClaw — chart scaffolding, values design, template patterns, dependency management, security hardening, and chart testing. Use when: user wants to create or improve Helm charts, design values.yaml files, implement template helpers, audit chart security (RBAC, network policies, pod security), manage subcharts, or run helm lint/test.

    The same file is in 4 other repositories

  • Prompt governance

    timdevai/proteus/skills/community/from-alireza/engineering/prompt-governance/skills/prompt-governance Skill

    1★ repo

    Use when managing prompts in production at scale: versioning prompts, running A/B tests on prompts, building prompt registries, preventing prompt regressions, or creating eval pipelines for production AI features. Triggers: 'manage prompts in production', 'prompt versioning', 'prompt regression', 'prompt A/B test', 'prompt registry', 'eval pipeline'. NOT for writing or improving individual prompts (use senior-prompt-engineer). NOT for RAG pipeline design (use rag-architect). NOT for LLM cost reduction (use llm-cost-optimizer).

    The same file is in 4 other repositories

  • Api test suite builder

    timdevai/proteus/skills/community/from-alireza/engineering/skills/api-test-suite-builder Skill

    1★ repo

    Use when the user asks to generate API tests, create integration test suites, test REST endpoints, or build contract tests.

    The same file is in 5 other repositories

  • Skill tester

    timdevai/proteus/skills/community/from-alireza/engineering/skills/skill-tester Skill

    1★ repo

    Validate, test, and score the quality of skills within the claude-skills ecosystem. Comprehensive meta-skill: structure validation, Python script testing (syntax + imports + runtime + output format), multi-dimensional quality scoring with letter grades and tier classification (BASIC/STANDARD/POWERFUL). Use when authoring a new skill, auditing existing skills for tier promotion, setting up pre-commit hooks for skill quality, or integrating skill QA into CI.

  • Statistical analyst

    timdevai/proteus/skills/community/from-alireza/engineering/statistical-analyst/skills/statistical-analyst Skill

    1★ repo

    Run hypothesis tests, analyze A/B experiment results, calculate sample sizes, and interpret statistical significance with effect sizes. Use when you need to validate whether observed differences are real, size an experiment correctly before launch, or interpret test results with confidence.

    The same file is in 4 other repositories

  • Ab test setup

    timdevai/proteus/skills/community/from-alireza/marketing-skill/skills/ab-test-setup Skill

    1★ repo

    When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "conversion experiment," "statistical significance," or "test this." For tracking implementation, see analytics-tracking.

    The same file is in 1 other repository

  • Dossier

    timdevai/proteus/skills/community/from-alireza/research/dossier/skills/dossier Skill

    1★ repo

    Decision-grade entity research skill — produces a hypothesis-tested dossier on a specific company, person, nonprofit, or government org, not a generic profile. Forcing intake makes the user state their hypothesis upfront (what they already believe and want to verify or disprove) so the dossier tests it rather than confirms it. Output is an editable Word document (.docx) with verdict on the hypothesis, identity facts, 12-month activity timeline, network signals, reputation signals, red flags, 3-5 conversation hooks tied to specific findings, and source-provenance audit log. Uses WebSearch + WebFetch + free APIs (SEC EDGAR, GitHub, ProPublica Nonprofit Explorer) as workhorses; optional BYOK MCPs (LinkedIn, Crunchbase, Apollo, Pitchbook, SimilarWeb) enhance coverage. Triggers: 'research [company]', 'dossier on [person/company]', 'background check on [entity]', 'prep me for a meeting with [person/company]', 'due diligence on [company]', 'what should I know about [entity]', 'research [person] before I [meet/hire/invest]', 'competitor research on [company]', 'investor diligence [company]', 'interview prep for [company]'. Honors sensitivity exclusions for journalism + personal-vetting contexts.

  • Tdd mastery

    timdevai/proteus/skills/community/from-rohitg00/tdd-mastery Skill

    1★ repo

    Test-driven development workflow with Red-Green-Refactor cycle across languages

  • Testing strategies

    timdevai/proteus/skills/community/from-rohitg00/testing-strategies Skill

    1★ repo

    Testing strategies including contract testing, snapshot testing, mutation testing, property-based testing, and test organization

  • Tdd flow

    timdevai/proteus/skills/tdd-flow Skill

    1★ repo

    Always-on multi-agent AI workstation for Claude Code. 142 specialist agents (ML, security, K8s, backend, frontend) · 366 curated skills · 200+ prompt templates · auto prompt-matcher · auto skill-matcher · MCP support · token router cuts Anthropic bill 6x via Kimi/Haiku/Ollama. LiteLLM · BYOK · MIT + Apache. One-line install.

  • Test driven development

    pgoell/pgoell-claude-tools/plugins/workbench/skills/test-driven-development Skill

    1★ repo

    Use when implementing any feature, bugfix, refactor, or behavior change before writing implementation code. Enforces test-first RED-GREEN-REFACTOR discipline.

  • React native test android visually

    lukas-hinterleitner/visual-app-skills/skills/react-native-test-android-visually Skill

    1★ repo

    Run a React Native or Expo app on a connected Android device or emulator, capture real screenshots via adb, read the Metro + logcat logs, and verify the visible UI and runtime behavior match what a recent code change intended. Use whenever the user asks to "test the app", "run it on Android", "see the visual changes", "verify a UI fix", "check if my change works/renders", or otherwise wants empirical on-device confirmation that a React Native / Expo change rendered correctly — even when they don't say "screenshot" or "logs". Handles starting Metro and the native build, waiting for the bundle + first frame, navigating with adb input, capturing the screen, reading Metro/logcat output (ReactNative / ReactNativeJS, Hermes, red-box errors), and reporting a concrete verdict with evidence. Covers bare React Native and Expo (dev client + run:android). Optionally diffs against a Figma reference when one is provided. Android only (iOS needs a Mac).

  • Workspace tests

    thepictishbeast/claude-tools/skills/workspace-tests Skill

    1★ repo

    Run cargo test --workspace across a list of Rust workspaces, failing fast and reporting which repo broke. Surfaces sibling-workspace regressions that single-repo hygiene cycles miss. Use when the user says "verify cross-repo tests", "run hygiene", "anything broken in sibling workspaces?", or as part of a /loop hygiene priority.

  • Edr evasion

    sunilgentyala/OmniRed/skills/infrastructure/edr-evasion Skill

    no license1★ repo

    EDR/AV evasion methodology for authorized red team operations. Covers process injection, AMSI bypass, ETW patching, LOLBins, reflective loading, and obfuscation techniques for testing endpoint detection coverage.

  • Scaffold and verify

    pricklywiggles/fractally-claude-marketplace/plugins/stack-it/skills/scaffold-and-verify Skill

    no license1★ repo

    Use this skill to prove a freshly installed project stack actually works before building anything real on it: generate the smallest example that exercises every chosen tool together, then run it until build, lint, tests, and the dev server are all green (plus a real-browser console check when there's a UI). This is the verification stage of the stack-it pipeline, after install-stack. Use it proactively, even when the user never says "verify", whenever a stack or its dependencies were just installed or scaffolded and someone wants confidence the pieces fit. Phrasings like "I just installed my stack, make sure it works", "build a minimal example that uses all of it and run it", "smoke-test my new project setup", "prove the stack works", "scaffold a smoke test", "keep fixing the example until tests/build/lint/the dev server pass", "do my pinned versions actually work together", or handing over a locked stack YAML plus an installed project and asking for confidence before building for real. It writes a thin end-to-end slice (e.g. a styled page with a form and one component test, or one API endpoint persisting through the ORM with a request test, or a CLI subcommand that runs), loops fix-and-retry until every check passes, and, when a chosen tool turns out broken or two pinned versions are fundamentally incompatible, stops and brings the user back to decide-stack rather than silently swapping or bumping. It does NOT design the architecture of the real app, and is not for choosing tools (use decide-stack), running the install commands (use install-stack), running or fixing tests in an existing or mature project, adding a dependency or feature to an app already under development, setting up CI configuration, or debugging a running production app.

  • Wnb viewmodel test

    wenubey/claude-android-skills/skills/wnb-viewmodel-test Skill

    1★ repo

    Use this skill when writing, reviewing, or refactoring a unit test for an Android ViewModel that follows the UDF contract (StateFlow<XxxState> + sealed XxxAction + onAction). Enforces the canonical test skeleton — @get:Rule MainDispatcherRule, TestDispatcherProvider(mainDispatcherRule.testDispatcher), factory function newViewModel(fake: FakeXxxRepository = FakeXxxRepository()), runTest { advanceUntilIdle() }, Truth assertions, Turbine for Flow/SharedFlow emissions, no Thread.sleep, no mocking of repository interfaces (use fakes). Triggers on "viewmodel test", "ViewModel unit test", "MainDispatcherRule", "TestDispatcherProvider", "runTest", "advanceUntilIdle", "Turbine", "fake repository", "test SharedFlow", "test one-shot event", "StandardTestDispatcher", "test coroutines", "Truth assertThat".

  • Add integration test

    tmj-90/gaffer/runner/skills/add-integration-test Skill

    1★ repo

    Use when a ticket asks for integration or end-to-end coverage across components — an API route hitting a database, a service-to-service call, a multi-step flow — rather than a single unit. Invoke for "test the endpoint end to end", "cover the checkout flow", or "verify the migration + query together".

  • Add unit test

    tmj-90/gaffer/runner/skills/add-unit-test Skill

    1★ repo

    Use when a ticket asks for new unit tests, or when an acceptance criterion requires test coverage for a function/module/component and none exists. Invoke for "add tests for X", "cover the Y edge case", or raising coverage on a specific unit.

  • Black box test

    tmj-90/gaffer/runner/skills/black-box-test Skill

    1★ repo

    Use as an INDEPENDENT tester agent to test another agent's `in_testing` ticket from the OUTSIDE — never your own, and never from the implementation diff. You test from the operational test contract + acceptance criteria only (never HOW it was built), writing automated tests that invoke the changed surfaces and recording a PASS/FAIL verdict via the scoped Dispatch MCP. The testing analog of the review gate — catches "the implementation passes its own tests but doesn't satisfy the acceptance criteria." Invoke whenever a ticket is `in_testing` and you are a different agent than the one who delivered it.

  • Fix flaky test

    tmj-90/gaffer/runner/skills/fix-flaky-test Skill

    1★ repo

    Use when a ticket reports an intermittently failing test — passes sometimes, fails others, or fails in CI but not locally. Invoke for "this test is flaky", "fix the intermittent failure in X", or "the suite is non-deterministic". Fix the root cause, never paper over it with a retry.

  • Run coverage

    tmj-90/gaffer/runner/skills/run-coverage Skill

    1★ repo

    Use when a ticket or acceptance criterion sets a coverage threshold or asks to raise coverage on a unit, and you need to measure and evidence it. Invoke for "coverage must stay above N%", "report the coverage delta", or "prove the new code is covered".

  • Run tests

    tmj-90/gaffer/runner/skills/run-tests Skill

    1★ repo

    Use when a ticket or acceptance criterion needs the test suite run and its result evidenced, or after making a change to confirm nothing broke. Invoke for "tests must pass", "verify the suite is green", or before submitting any code change for review.

  • Self review

    tmj-90/gaffer/runner/skills/self-review Skill

    1★ repo

    Use after implementing a ticket and after its tests pass, but before submitting for review, to review your own diff as a skeptic would. Checks the finished `git diff` against every acceptance criterion (is each genuinely satisfied?), against scope (did you change only what the ticket needs?), and against quality (bugs, leftover debug, missed edge cases, repo conventions). If the diff reveals a gap, fix it and re-test before submitting. Invoke whenever implementation is complete and tests are green and you are about to hand the ticket to review.

  • Api test

    morganmuli/metaskill/examples/fullstack-web/.claude/skills/api-test Skill

    1★ repo

    Run API integration tests against the running backend, verify endpoints return expected responses and status codes. Use after deploying a preview or starting the dev server.

    The same file is in 1 other repository

  • Build and test

    morganmuli/metaskill/examples/fullstack-web/.claude/skills/build-and-test Skill

    1★ repo

    Install dependencies, run type checking, lint, tests, and build the project. Use after making code changes to verify nothing is broken.

    The same file is in 1 other repository

  • Build and test

    morganmuli/metaskill/examples/ios-app/.claude/skills/build-and-test Skill

    1★ repo

    Build the Xcode project and run the full test suite. Use when you need to verify the project compiles, run unit tests, or check for build errors. Reports pass/fail results with detailed error output.

    The same file is in 1 other repository

  • Shipkit test cases

    stefan-stepzero/shipkit/install/skills/shipkit-test-cases Skill

    1★ repo

    Generate and maintain code-anchored test case specifications. Use when setting up test coverage, reviewing what to test, or before team implementation.