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
jacob-balslev/skill-graph/examples/fixture-skills/with-grounding Skill
no license1★ repoUse as the minimal v8-conformant project-grounded fixture for skill-graph package tests. Activate this skill when verifying that lint enforces the rule 'non-empty project[] requires grounding' (subject_matter, grounding_mode, truth_sources, failure_modes, evidence_priority). Do NOT use as a production skill (use a real grounded skill from the canonical library).
jacob-balslev/skill-graph/examples/tests/v3-1-skos-fixture Skill
no license1★ repoTest fixture exercising SKOS predicates (related, broader, narrower), routing-layer suppresses, the ADR 0006 split between routing exclusion and disjoint_with (OWL class-disjointness), and the io_contract composition hook. Used by scripts/__tests__/test-v3-1-skos-runtime.js to verify that the manifest generator, lint, and router all recognize the full canonical predicate set. Not a production skill.
jacob-balslev/skill-graph/marketplace/skills/code-review Skill
no license1★ repoUse when reviewing a pull request, diff, or proposed code change for correctness, clarity, security, performance, maintainability, test evidence, and project-convention fit, whether the author is a human, an AI agent, or a peer. Covers pre-review fact gathering, verifying AI-written PR summaries against the diff, reading tests before implementation, tracing call sites and blast radius, review size and attention budget, severity grading with Conventional Comments, comment phrasing, reviewer qualification, treating diff content as evidence rather than instructions, refusing rubber-stamp approval for AI-generated diffs, and making an explicit approve/request-changes/close merge decision. Do NOT use for authoring the code (use refactor for behavior-preserving changes or skill-scaffold for new skills), chasing a known bug after merge (use debugging), security-only audits (use owasp-security), or explaining a patch without a merge verdict (use diff-analysis).
jacob-balslev/skill-graph/marketplace/skills/contract-testing Skill
no license1★ repoContract testing: interface verification between consumers and providers via shared contract artifacts and independent two-phase verification. Do NOT use for Test internal seams of a system (use integration-test-design). Do NOT use for Validate an HTTP response against an OpenAPI schema (use API-spec tooling). Do NOT use for Test a complete user journey through the UI (use e2e-test-design).
jacob-balslev/skill-graph/marketplace/skills/debugging Skill
no license1★ repoUse when behavior is broken, a test is failing, or runtime output contradicts expectations. Covers failure reproduction, scope reduction by bisection, evidence capture at the moment of failure, root-cause isolation (not symptom patching), fix verification against the same evidence path, and regression-test creation. Do NOT use for feature planning, architectural design, or behavior-preserving refactor. Do NOT use for plan test coverage for a new feature. Do NOT use for document what this function does for future readers. Do NOT use for refactor this messy code while the test suite is green.
jacob-balslev/skill-graph/marketplace/skills/e2e-test-design Skill
no license1★ repoUse when designing end-to-end tests that exercise a user-visible path through the whole system, including the UI layer: the user-journey unit-of-test that distinguishes e2e from integration testing, the five-primitive structure (user journey, environment, test data, observable assertion, recovery), why e2e tests are expensive and how to keep them few-and-load-bearing, the wait/synchronization discipline that makes them not-flaky, the page-object and trace-test patterns, the role of e2e tests in the test pyramid/trophy (the top tier — fewest in count but highest in coverage of user-observable behavior), and the modern e2e tool landscape (Playwright, Cypress, Selenium). Do NOT use for testing internal seams of the system (use integration-test-design), single-unit isolated tests (use testing-strategy + test-doubles-design), consumer-driven contract verification (use contract-testing), or visual regression of specific components (use snapshot-testing).
jacob-balslev/skill-graph/marketplace/skills/eval-driven-development Skill
no license1★ repoUse when building language-model-integrated systems by writing evaluations before and alongside the system: the statistical (not binary) nature of LLM evals, the five primitives (dataset, evaluation function, aggregation, iteration loop, regression budget), the judgment-mechanism taxonomy (programmatic, model-graded, human-graded, preference comparison), the eval-surface stack (final response, trajectory/tool-use, retrieval/RAG, safety, cost), the statistical-significance discipline (paired tests, bootstrap CI on the delta, minimum-detectable-effect), trajectory-vs-final-output evaluation for multi-step agents, judge calibration and bias, Goodhart's Law and suite saturation, and the offline-eval-vs-production-telemetry distinction. Do NOT use for deterministic unit testing or general TDD (use testing-strategy), production monitoring (use evaluation or error-tracking), or building individual eval rubrics and task sets (use agent-eval-design — it owns construction; this skill owns iteration discipline).
jacob-balslev/skill-graph/marketplace/skills/evaluation Skill
no license1★ repoUse when scoring a completed agent task, implementation, document, skill upgrade, or other deliverable against the original request, acceptance criteria, verification evidence, quality rubric, and residual risks before calling it done. Covers skeptical critic review, 1-5 scoring, score ceilings, evidence sufficiency, finding/action capture, and the evaluation-revision loop. Do NOT use for designing eval datasets or graders (use eval-driven-development), line-by-line diff review (use code-review), choosing test levels (use testing-strategy), or designing the overall process and gates before work starts (use methodology). Do NOT use for design a new eval dataset, grader, and hard negatives for this router. Do NOT use for review this pull request line by line for bugs and security issues. Do NOT use for choose unit versus integration versus end-to-end tests for this feature. Do NOT use for design the whole implementation methodology and quality gate sequence before work starts.
jacob-balslev/skill-graph/marketplace/skills/integration-test-design Skill
no license1★ repoUse when designing tests that verify the interaction between two or more units of a system — modules, services, layers, processes: the scope-and-boundary primitives that distinguish integration from unit and e2e tests, the test-pyramid (Cohn 2009) and test-trophy (Dodds) frameworks for how much integration testing belongs in the suite, the real-vs-faked-collaborator decision per dependency, the test-data lifecycle (per-test setup, transaction rollback, container reset), the difference between sociable-unit tests, integration tests, and contract tests, and the failure modes (over-broad scope that mimics e2e, over-narrow scope that mimics unit, shared mutable state that produces flakes). Do NOT use for testing one unit in isolation (use testing-strategy + test-doubles-design), full user-journey testing (use e2e-test-design), consumer-driven contract verification (use contract-testing), or test-suite quality measurement (use mutation-testing).
jacob-balslev/skill-graph/marketplace/skills/lint-overlay Skill
no license1★ repoUse when adding or enforcing lint rules as part of a test or verification plan. Extends testing-strategy with lint-specific guidance: rule selection, gate placement, failure triage, and migration planning when introducing rules to an existing codebase. Do NOT use standalone — load the base testing-strategy skill alongside it — and do NOT use for chasing a specific lint failure in one file (that is debugging). Do NOT use for decide whether to unit-test or integration-test this handler. Do NOT use for extract this repeated code pattern into a shared util.
jacob-balslev/skill-graph/marketplace/skills/mckinsey-7s Skill
no license1★ repoUse when diagnosing organizational alignment with the McKinsey 7S framework: shared values, strategy, structure, systems, style, staff, and skills; how the seven elements reinforce or conflict; change-readiness gaps; and implementation risks. Covers internal organization effectiveness, operating-model alignment, transformation diagnostics, post-merger integration checks, and strategy-to-execution gap analysis. Do NOT use for external industry profit-pressure diagnosis (use porters-five-forces), activity-level value and cost mapping (use value-chain-analysis), durable resource advantage testing (use vrio), broad internal/external option generation (use swot-tows), or execution goal-setting alone (use okrs). Do NOT use for Analyze buyer power, supplier power, substitutes, entrants, and rivalry in this industry. Do NOT use for Map the value chain activities that create customer value and drive cost. Do NOT use for Use VRIO to test whether our data, brand, and process are durable advantages.
jacob-balslev/skill-graph/marketplace/skills/methodology Skill
no license1★ repoUse when planning multi-step implementations, designing quality gates, establishing verification protocols, or building agent checklists calibrated to known failure modes. Covers methodology/method/process distinctions, Cleanroom, PSP/TSP, hypothesis-driven development, DMAIC, checklist design, V&V frameworks, EDDOps, quality gates, and PDCA. Do NOT use for code-review verdicts (use `code-review`), behavior-preserving implementation work (use `refactor`), or test strategy (use `testing-strategy`). Do NOT use for review this PR and decide whether to approve it. Do NOT use for refactor this file while preserving behavior. Do NOT use for decide unit vs integration vs e2e coverage for this feature. Do NOT use for write the eval cases and grader rubric for this router. Do NOT use for block this dangerous git command or secret-bearing tool call.
jacob-balslev/skill-graph/marketplace/skills/mutation-testing Skill
no license1★ repoUse when reasoning about mutation testing as a behavioral signal of test-suite quality: the mutant-operator vocabulary (replace operator, negate condition, flip Boolean, remove statement, alter constant), the mutation-score metric (killed mutants / total non-equivalent mutants), why mutation testing is a stronger signal than code coverage (coverage measures execution; mutation measures whether the tests would catch a defect), the equivalent-mutant problem (mutants that produce no observable behavior change despite syntactic difference), selective and incremental mutation strategies that make the technique practical for large codebases (PIT, Stryker), and the relationship between mutation testing and TDD. Do NOT use for the structural signal of how much code tests reach (use test-coverage-strategy), the construction of test doubles (use test-doubles-design), the strategic question of what to test at which level (use testing-strategy), or generic fault injection at runtime (use chaos-engineering).
jacob-balslev/skill-graph/marketplace/skills/pattern-recognition Skill
no license1★ repoUse when auditing for recurring issues, clustering errors, detecting drift from conventions, or when an agent keeps fixing symptoms instead of root causes. Covers the Observe -> Cluster -> Name -> Codify -> Detect -> Prevent loop, grep-based audits, normalize-then-hash error clustering, board-health patterns, design-token and heading drift, domain-encoding patterns, eval-as-pattern-tests, 5 Whys, pattern lifecycle states, and drift traps. Do NOT use for one-off bug localization without recurrence, or for designing the classification system itself; this skill detects violations of conventions that already exist. Do NOT use for review this code for semantic correctness. Do NOT use for find where the user-auth helper is defined. Do NOT use for design a MECE classification taxonomy for our error catalogue. Do NOT use for investigate why this single failing test is breaking. Do NOT use for trigger an alert when CPU exceeds 80% for 5 minutes. Do NOT use for rewrite this function to be cleaner.
jacob-balslev/skill-graph/marketplace/skills/performance-testing Skill
no license1★ repoUse when measuring a system's non-functional properties — latency, throughput, error rate, resource utilization, saturation — by running it under controlled load and verifying against explicit SLO thresholds. Covers the five primitives (load profile, workload, latency metric, throughput metric, SLO target), load-shape taxonomy (smoke, load, stress, spike, soak, breakpoint), latency-percentile vocabulary (p50, p95, p99, p99.9), why average latency and coordinated omission mislead, tool selection (k6, JMeter, Locust, Gatling, Vegeta), and offline controlled measurement versus production observability. Do NOT use for optimization itself (use `performance-engineering`), threshold contracts (use `performance-budgets`), production runtime measurement (use `observability-modeling` or `error-tracking`), single-function microbenchmarks, fault injection, or test-suite quality measurement (use `mutation-testing`). Do NOT use for decide which modules need more unit tests and what test coverage target to enforce.
jacob-balslev/skill-graph/marketplace/skills/problem-framing Skill
no license1★ repoUse when a team is converging on solutions before agreeing on the problem, when a brief reads as a feature request, when symptoms and root needs are tangled, or when assumptions need surfacing before design work proceeds. Do NOT use for code-level bug triage, runtime failure diagnosis, or root-cause analysis of system errors — those are engineering investigation tasks, not design problem framing. Do NOT use for Find the bug causing the 500 error in the checkout endpoint. Do NOT use for Why is the test suite flaky on CI? Do NOT use for Classify whether this agent request is high-risk before executing.
jacob-balslev/skill-graph/marketplace/skills/property-based-testing Skill
no license1★ repoUse when reasoning about tests that specify universal properties of code rather than specific input-output pairs: the forall(input) → property quantification, the generator/shrinker primitives that produce inputs and minimize failing cases, the four-rules-of-simple-design analog (commutativity, associativity, idempotence, round-trip, oracle, invariant), the difference between example-based tests (one input, one assertion) and property-based tests (many generated inputs, one universal claim), why property tests find bugs example tests don't, the shrinking discipline that produces minimal failing cases, and the trade-off between generator complexity and bug-finding capacity. Do NOT use for specifying one concrete behavior with one input (use example-based tests under testing-strategy), for fuzz-testing focused on crashes (use fuzz-testing), for mutation testing as a test-suite quality signal (use mutation-testing), or for model-based testing of state machines (use state-machine-modeling).
jacob-balslev/skill-graph/marketplace/skills/snapshot-testing Skill
no license1★ repoUse when reasoning about snapshot testing as a tactical technique: capture-and-compare against a reviewed baseline, data snapshots, DOM snapshots, text/file snapshots, visual snapshots, approval-cycle discipline, snapshot churn, unstable inputs, large unreadable diffs, golden files, characterization tests, and visual regression review with tools such as Jest, Vitest, Playwright screenshots, Storybook/Chromatic, and Percy. Do NOT use for the overall test-level mix (use `testing-strategy`), universal property claims (use `property-based-testing`), test double construction (use `test-doubles-design`), strict test-first workflow design (use `test-driven-development`), or end-to-end user journey design (use `e2e-test-design`). Do NOT use for choose the overall unit integration e2e and performance test mix for this feature. Do NOT use for use property-based testing with fast-check generated arrays to assert sort output is ordered and preserves items.
jacob-balslev/skill-graph/marketplace/skills/spec-driven-development Skill
no license1★ repoUse when starting a non-trivial feature, refactor, or agent implementation that needs a written spec, plan, task breakdown, and verification path before code changes. Covers Spec Kit-style SDD phases, requirements-vs-plan separation, task traceability, review gates, and spec-compliance verification. Do NOT use for one-line edits, README-only fixes, post-implementation code review (use `code-review`), or test-level decisions (use `testing-strategy`).
jacob-balslev/skill-graph/marketplace/skills/test-coverage-strategy Skill
no license1★ repoUse when reasoning about code coverage as a strategic measurement rather than a quality target: structural reach versus behavioral verification (covered vs tested), the coverage-criterion hierarchy (function, line, branch, decision, condition, MC/DC, path) and matching the criterion to where a module's failure modes hide, Marick's floor-vs-ceiling distinction, Goodhart's Law applied to coverage and Goodhart-resistant policy (diagnostic use, diff/patch floors, risk-weighting, behavioral panels), denominator hygiene and cross-tool counter semantics, safety-critical MC/DC (DO-178C Level A required; ISO 26262 ASIL-D highly recommended) as requirements-based evidence, and interpreting coverage from AI-generated tests. Do NOT use for choosing test levels (use testing-strategy), mutation testing as a behavioral signal (use mutation-testing), test-double construction (use test-doubles-design), LLM eval iteration (use eval-driven-development), or specific coverage-tooling configuration (tool docs).
jacob-balslev/skill-graph/marketplace/skills/test-doubles-design Skill
no license1★ repoUse when designing or reviewing test doubles — the stand-in objects that replace real collaborators in a test: the five-kind taxonomy (dummy, stub, spy, fake, mock) from Meszaros's xUnit Test Patterns, the difference between state verification (Detroit-school, classicist) and interaction verification (London-school, mockist) and how it determines which doubles fit, the cost of doubles (fragility, false confidence, divergence from real behavior), the role of fakes as the under-used middle ground, the verify_with relationship to test-driven-development, and the heuristics for when to use a real collaborator instead of any double. Do NOT use for choosing test levels or what to test (use testing-strategy), the design discipline of writing tests first (use test-driven-development), specific mocking-library API choice (library docs), or general production stubs and feature flags (use feature-gating or domain-specific skills). Do NOT use for set up a production feature flag (use feature-gating).
jacob-balslev/skill-graph/marketplace/skills/test-driven-development Skill
no license1★ repoUse when reasoning about Test-Driven Development as a design discipline rather than a workflow: the red-green-refactor cycle as a feedback loop, the difference between London-school (outside-in, interaction-heavy, mock-driven) and Detroit-school (inside-out, state-heavy, classicist) TDD, the role of TDD as a design tool (how tests pressure code into more decomposable shapes), the connection between TDD and emergent design, the boundary between TDD and prior-test-suites, why TDD's failure mode is not 'no tests' but 'tests that mirror implementation', and the empirical record of TDD's effects on defect density, design quality, and development velocity. Do NOT use for the strategy of what to test at which level (use testing-strategy), the construction of test doubles (use test-doubles-design), the discipline of LLM eval iteration (use eval-driven-development), or general-software process workflow (use the obra/superpowers test-driven-development workflow skill — this skill is the concept-shape complement).
jacob-balslev/skill-graph/marketplace/skills/testing-strategy Skill
no license1★ repoUse when planning tests for a bug fix, feature, or refactor — deciding what deserves a test, at which level, with what evidence. Covers test-scope decisions, test-level selection (unit / integration / contract / e2e), effort-to-risk matching, regression targeting, evidence quality, and failure-case coverage. Do NOT use for chasing a known failure (that is `debugging`), for pure doc writing (that is `documentation`), or for conceptual architecture discussion with no verification target (no dedicated skill — treat as strategy, not testing). Do NOT use for my existing test is failing — why? Do NOT use for write a testing-patterns guide for the contributor docs. Do NOT use for clean up this duplicated test setup across three files.
jacob-balslev/skill-graph/marketplace/skills/usability-testing Skill
no license1★ repoUse when observing representative real users attempting realistic tasks on a prototype or live product to surface usability issues: moderated or unmoderated, remote or in-person, concurrent or retrospective think-aloud, task scenarios, participant screening, tree/first-click testing for IA findability questions, pilot runs, severity rating, sample sizing by claim type, and ethical recording/consent. Do NOT use for automated test suites, code coverage, CI pipelines, unit/integration testing, load testing, or replacing participants with AI/synthetic users; those are engineering verification or synthetic-analysis concerns, not human-behavior observation. Do NOT use for Add unit tests for the order-total calculation function. Do NOT use for Set up the CI pipeline for the new repo. Do NOT use for Run a load test against the checkout API. Do NOT use for Run a card sort to design the navigation hierarchy and labels for this site. Do NOT use for Cluster the findings from ten completed user sessions into themes.
itsyasirkhandev/spec-driven-development/skills/development/tdd Skill
no license1★ repoTest-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.
The same file is in 17 other repositories
itsyasirkhandev/spec-driven-development/skills/matt pocock/tdd Skill
no license1★ repoTest-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.
The same file is in 17 other repositories
almasumdev/awesome-java-android-agent-skills/.github/skills/testing_and_automation/espresso-java Skill
no license1★ repoExpert guidance on Android UI testing in Java with Espresso, IdlingResource, Hilt test rules, and Robolectric for fast JVM UI tests. Use this when writing instrumented tests, replacing flaky sleeps, or setting up a hermetic UI test harness.
almasumdev/awesome-java-android-agent-skills/.github/skills/testing_and_automation/junit-mockito Skill
no license1★ repoExpert guidance on unit testing Java Android code with JUnit, Mockito, and parameterized tests for ViewModels, repositories, and use cases. Use this when writing or reviewing JVM-side unit tests.
diamitani/rostr-agent/optional-skills/dogfood/adversarial-ux-test Skill
1★ repoRoleplay the most difficult, tech-resistant user for your product. Browse the app as that persona, find every UX pain point, then filter complaints through a pragmatism layer to separate real problems from noise. Creates actionable tickets from genuine issues only.
The same file is in 1 other repository
diamitani/rostr-agent/optional-skills/security/web-pentest Skill
1★ repoAuthorized web application penetration testing — reconnaissance, vulnerability analysis, proof-based exploitation, and professional reporting. Adapts Shannon's "No Exploit, No Report" methodology with hard guardrails for scope, authorization, and aux-client leakage. Active testing against running applications you own or have written authorization to test.
diamitani/rostr-agent/skills/software-development/test-driven-development Skill
1★ repoTDD: enforce RED-GREEN-REFACTOR, tests before code.
The same file is in 1 other repository
yli769227-jpg/agent-discipline/skills/test-is-truth Skill
1★ repoTests are the truth. "Done" means a verifiable test result, not "the code is written". Triggers before you tell the human a task is complete, before saying "should work", before merging a PR or closing an issue, and before handing a sub-task to another agent. Any completion claim must carry a ✅/❌/⚠️ three-part test conclusion. 测试即结论:完成 = 可验证的测试结果,不是"代码写完了"。任何完成声明必须附 ✅/❌/⚠️ 三段式结论。
yli769227-jpg/agent-discipline/skills/test-quality Skill
1★ repoTest quality nine rules. test-is-truth demands that "done" is backed by a test verdict; this skill governs whether the tests themselves are worth trusting. Coding agents over-generate tests: mock-heavy suites asserting implementation details, near-duplicate bodies differing by one value, tests that re-verify the framework. Triggers when about to write or generate tests, review a diff containing tests, or QA-review a sub-agent's test output. 测试质量九规:test-is-truth 管"完成必须有测试结论",本 skill 管"测试本身写得好不好"。agent 会过度生成测试——mock 堆山、近似重复、测框架不测逻辑。
kwhorne/elyra-skills/skills/laravel-testing Skill
1★ repoTest Laravel applications effectively with Pest or PHPUnit - feature vs unit boundaries, factories, database strategy, what to fake, and HTTP/Livewire assertions. Use when writing tests for Laravel code, reviewing a Laravel test suite, deciding how to test a controller, job, or command, or when tests are slow or brittle.
kwhorne/elyra-skills/skills/test-writing Skill
1★ repoDecide what to test, structure tests with arrange/act/assert, and avoid common pitfalls. Use when the user asks to write, add, or improve tests for existing code, or wants test coverage for a new feature.
almasumdev/awesome-react-native-agent-skills/.github/skills/testing_and_automation/rn-e2e-testing Skill
no license1★ repoExpert guidance on end-to-end testing React Native apps with Maestro or Detox, including CI setup and flake reduction. Use when asked about E2E, UI automation, Maestro, or Detox.
almasumdev/awesome-react-native-agent-skills/.github/skills/testing_and_automation/rn-testing Skill
no license1★ repoExpert guidance on unit and component testing in React Native with Jest and React Native Testing Library, including hook tests, mocks, and snapshot discipline. Use when asked about unit tests, component tests, or mocks.
brenbuilds1/skills/skills/unclebob Skill
1★ repoA do-not-read-the-code workflow for delegating implementation to a coding agent. Use when handing an agent a feature or a fix you do not intend to review line by line. The agent turns the request into human-approved gherkin scenarios, writes failing tests and locks them before writing any implementation, then runs the result through machine-checked constraints: unit tests, acceptance scenarios, changed-line coverage, mutation testing on both the code and the gherkin examples, quality metrics, the project's own checks, plus a torture round (property, performance, jitter tests) where the change warrants it. The human reads a one-table receipt instead of the diff. The test lock and the mutation constraint exist because the same agent writes both the code and the tests.
MarcoAntolini/cursor-sync/agents/skills/mattpocock/engineering/tdd Skill
no license1★ repoTest-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
The same file is in 9 other repositories
MarcoAntolini/cursor-sync/agents/skills/testing/playwright-best-practices Skill
no license1★ repoUse when writing Playwright tests, fixing flaky tests, debugging failures, implementing Page Object Model, configuring CI/CD, optimizing performance, mocking APIs, handling authentication or OAuth, testing accessibility (axe-core), file uploads/downloads, date/time mocking, WebSockets, geolocation, permissions, multi-tab/popup flows, mobile/responsive layouts, touch gestures, GraphQL, error handling, offline mode, multi-user collaboration, third-party services (payments, email verification), console error monitoring, global setup/teardown, test annotations (skip, fixme, slow), test tags (@smoke, @fast, @critical, filtering with --grep), project dependencies, security testing (XSS, CSRF, auth), performance budgets (Web Vitals, Lighthouse), iframes, component testing, canvas/WebGL, service workers/PWA, test coverage, i18n/localization, Electron apps, or browser extension testing. Covers E2E, component, API, visual, accessibility, security, Electron, and extension testing.
The same file is in 1 other repository
paulnsorensen/skillz-that-grillz/skills/ralphify-spec Skill
1★ repoGenerate a ralphify-approved ralph directory (RALPH.md + optional scripts) from a plain-English description of repetitive or iterative work. Use this skill whenever the user says "ralphify", "create a ralph", "ralph wiggum", "autonomous loop", "/ralphify", references Geoffrey Huntley's Ralph Wiggum method, or asks to wrap iterative work in ralphify (test-until-green, refactor-until-done, lint-until-clean, coverage-until-90, burn-down-todos, resolve-review-comments). Trigger even when the user does not explicitly name ralphify but describes an open-ended loop ("keep fixing tests until they pass", "port files one by one until the directory is done"). Do not trigger for one-shot tasks — ralphs exist for work that benefits from running N times against a stop condition.
timeyour/agentskills-audit-collection/.claude/skills/flow-test Skill
1★ repoTest every visible function and user workflow in a website, web app, or open-source project. Use for live QA: navigation, CTAs, forms, auth, search, upload, checkout, dashboards, error states, mobile behavior, expected vs actual results, and issue cards with copyable fixes.
timeyour/agentskills-audit-collection/.claude/skills/physical-flow-test Skill
1★ repoGenerate executable real-browser flow tests using Python Playwright from business flows. Use when cognitive audit, flow-test, audit, or accept-five needs physical browser proof for CTA, form, auth, upload, checkout, dashboard, production, staging, or local workflows.
almasumdev/awesome-kotlin-multiplatform-agent-skills/.github/skills/testing_and_automation/compose-multiplatform-testing Skill
no license1★ repoTesting Compose Multiplatform UI — semantic assertions in commonTest, running UI tests on Android / Desktop / iOS, and screenshot regression strategies. Use when covering shared UI with tests.
almasumdev/awesome-kotlin-multiplatform-agent-skills/.github/skills/testing_and_automation/kmp-testing Skill
no license1★ repoTesting strategy for KMP — `commonTest` with `kotlin.test`, `expect`/`actual` test doubles, Turbine for Flow assertions, Ktor `MockEngine`, and in-memory SQLDelight drivers. Use when writing tests for shared code.
justincordova/agents/skills/testing Skill
1★ repoUse when writing tests, deciding what to test, or choosing testing approaches. Practical guidance for test design and strategy.
geigermatic/claude-craft/skills/tdd-slice Skill
1★ repoPlan a feature as vertical slices with contract test → implementation → e2e → flag-gated deploy. Use when starting non-trivial customer-facing feature work, especially anything proxying an external service or requiring revert speed.
zoidbergclawd/coherence/skills/verification-as-context Skill
1★ repoUse when implementing or changing behavior, adding tests, choosing test level, or deciding what proof must ride with a change, to treat tests, docs, and CI as executable context that preserves product intent across fast agentic changes.
ChristopherAlphonse/calphonse-skills/jest-react-testing Skill
1★ repoComprehensive React component testing with Jest and React Testing Library covering configuration, mocking strategies, async testing patterns, hooks testing, and integration testing best practices
ChristopherAlphonse/calphonse-skills/plan-review-tests Skill
1★ repoProduces a test diagram, identifies coverage gaps, and writes a .planning QA handoff artifact.
ChristopherAlphonse/calphonse-skills/playwright-cli Skill
1★ repoAutomate browser interactions, test web pages and work with Playwright tests.
ChristopherAlphonse/calphonse-skills/qa-only Skill
1★ repoReport-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.
endalk200/skills/skills/tdd Skill
no license1★ repoCollection of agent skills I use in day to day work spanning engineering and none engineering work.
The same file is in 1 other repository
ravihammond/skills/skills/tdd Skill
1★ repoTest-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
liuqi1024/matrix-boot/skills/integration-test-guide Skill
1★ repoGuide integration testing, performance testing, release readiness, and quality gates for staged software projects. Use when planning or reviewing integration tests, test data, environment dependencies, API test collections, performance tests, release checks, rollback plans, or project acceptance gates.
agentjido/jido-skills/.agents/skills/jido-testing Skill
1★ repoTest Jido agents and actions effectively without OTP processes. Use when writing tests for agents, actions, plugins, or signal handling. Covers unit testing, property-based testing, and integration testing patterns.
agentjido/jido-skills/.cursor/skills/jido-testing Skill
1★ repoTest Jido agents and actions effectively without OTP processes. Use when writing tests for agents, actions, plugins, or signal handling. Covers unit testing, property-based testing, and integration testing patterns.
agentjido/jido-skills/.gemini/skills/jido-testing Skill
1★ repoTest Jido agents and actions effectively without OTP processes. Use when writing tests for agents, actions, plugins, or signal handling. Covers unit testing, property-based testing, and integration testing patterns.
agentjido/jido-skills/source/skills/jido-testing Skill
1★ repoTest Jido agents, actions, plugins, signals, directives, and AI integrations with focused unit and runtime coverage. Use when adding tests, fixing test gaps, or validating Jido behavior.
fbarrento/laravel-agent-kit/.agents/skills/tdd Skill
no license1★ repoTest-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.
The same file is in 17 other repositories