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

  • Experiments

    ajstars1/startup-coach/experiments Skill

    0★ repo

    Design and grade validation experiments — price tests, concierge/manual MVPs, landing/smoke tests, channel tests, pre-sales — as test cards with explicit hypotheses, metrics, and pass/fail bars. Use when an assumption can't be validated by interviews alone (especially willingness to pay — only refusable prices produce truth), when choosing an MVP, or when a founder reports experiment results.

  • Tests that matter

    yakoshiq/skills/skills/tests-that-matter Skill

    0★ repo

    Write or review tests that prove observable behavior, failure semantics, invariants, and boundary cases. Use when adding tests, fixing brittle or mock-heavy tests, reviewing test quality, or when coverage exists but confidence does not.

  • Creative testing framework

    gmmh1/claude-paid-media-skills/skills/creative-testing-framework Skill

    0★ repo

    Design statistically sound creative tests — sample size, variable isolation, and significance — for any advertising platform. Triggers on 'how should I test this ad', 'is this result statistically significant', 'A/B test my creative', or 'how many impressions do I need before judging this'. Platform-agnostic testing methodology feeding every platform's optimization skill.

  • Pre push

    MrToAster13/mrtoaster13-plugins/plugins/autonomous-workflows/skills/pre-push Skill

    0★ repo

    Pre-push orchestrator — detect Python/Node stack, then run simplify, review, security, test, commit as gated stages (retry flaky network, chmod +x scripts, stop on real failures). Use when ready to push to main, or on "pre-push", "clean up before pushing", "polish and commit", "finalize", "ship it".

  • Remediate

    MrToAster13/mrtoaster13-plugins/plugins/autonomous-workflows/skills/remediate Skill

    0★ repo

    Self-driving, test-verified remediation loop. Reads REMEDIATION_PLAN.md (or drafts one and gets your OK), then implements each phase, runs the full suite, and iterates until green — without editing tests to fake it. Commits each green phase to a branch and drafts a ready-to-run push/PR. Use when the user says "remediate", "run the remediation plan", "fix until tests pass", "self-drive these fixes", or points at a plan of bugs to work through.

  • Test plan

    muzalee/claude-atelier/skills/test-plan Skill

    no license0★ repo

    Write a short test plan for a change before implementing — list the cases that must pass, what to break to prove them, and what NOT to test. Use before starting non-trivial work, when asked for a "test plan", or when reviewing a PR to sanity-check coverage.

  • Test placeholder data

    SkillMedev/live-data/skills/test-placeholder-data Skill

    0★ repo

    Use when building a demo, prototype, or tutorial that needs realistic remote data - "fake products/users/todos for this app", "an API I can hit while wiring up fetch", "placeholder images", "seed this UI with something that looks real", or teaching HTTP/CRUD against a live endpoint. DummyJSON is the default (rich e-commerce-shaped data, full fake CRUD, no key); JSONPlaceholder, RandomUser, and Lorem Picsum cover the rest. Do NOT use for generating local test fixtures or factories inside a test suite - use test-data-builder instead; do NOT use when the task needs real-world data (weather, prices, countries) - route through public-data-api-picker.

    The same file is in 1 other repository

  • Ship it for real

    lexthirteen-ai/founder-survival-kit/skills/ship-it-for-real Skill

    0★ repo

    Turns "it worked when I tried it" into a repeatable check that survives real users. Helps a founder write down the handful of things their app must always do, turn those into a simple test they can rerun after every change, and close the gap between a demo that works and a product that holds up on real, messy input. Use when an app or agent works in the demo but breaks on real users, when changes keep breaking things that used to work, or before relying on something in production. Builds a repeatable check, not a test suite.

  • Bug hunt

    ccpowerpack/claude-code-skills/skills/bug-hunt Skill

    0★ repo

    Systematic root-cause debugging loop — reproduce, isolate, instrument, fix, prove. Use when investigating a bug, crash, flaky test, regression, or any "why is this broken / not working / behaving weirdly" request. Refuses to patch symptoms without a confirmed root cause.

  • Test first

    ccpowerpack/claude-code-skills/skills/test-first Skill

    0★ repo

    Enforced test-driven development — write the failing test, run it to prove it fails, then implement until green. Use when the user asks to build a feature "with TDD", "test-first", or wants high-confidence implementation of well-specified behavior.

  • Swift ci portability

    chsistrying/swift-ship-skills/skills/swift-ci-portability Skill

    0★ repo

    Sets up GitHub Actions CI for Swift Package Manager projects (minimal macOS build+test workflow, Xcode/macOS version matrix, .build caching, runner image selection) and diagnoses/prevents environment-dependent Swift bugs that pass locally but fail on CI (JSONDecoder ISO8601 fractional seconds, NumberFormatter locale grouping, Date/timezone assumptions, locale-dependent string sorting, hardcoded paths, filesystem case-sensitivity, Bundle.module resource paths, Decimal/Double formatting). Use when asked for "swift CI", "GitHub Actions swift test", when "tests pass locally but fail on CI", or when debugging "locale" or "Foundation differences" between macOS/Xcode versions. Trigger with "/swift-ci-portability".

  • Test protocol

    nubasu/Pseudo-Fable-Framework/frameworks/pseudo-fable-lift/.claude/skills/test-protocol Skill

    0★ repo

    Write tests that actually catch bugs — behavior over implementation, fail-first proof (never trust a test you haven't seen red), minimal mocking, mandatory boundary and error-path coverage, deterministic construction, flaky elimination, characterization tests before changing untested code. Use when writing or modifying tests, when a change needs coverage, or when a suite is green but untrustworthy.

  • Alterlab rma statistics guide

    prone-dc302/AlterLab-FC-Skills/skills/rma/alterlab-rma-statistics-guide Skill

    0★ repo

    This skill should be used when the user asks about "statistics", "statistical analysis", "SPSS", "R statistics", "hypothesis testing", "t-test", "ANOVA", "chi-square", "regression analysis", "correlation", "p-value", "effect size", "confidence interval", "descriptive statistics", "inferential statistics", "data visualization", "act as a statistics guide", "statistics guide mode", "statistical significance", "research statistics", "quantitative analysis", "normal distribution", "sample size", "power analysis", "non-parametric tests", "Mann-Whitney", "Kruskal-Wallis", "Likert scale analysis", "survey data analysis", "Excel statistics", "JASP", "factor analysis", "reliability analysis", "Cronbach's alpha", "research data analysis", or needs expertise in applying statistical methods to academic research data. Part of the AlterLab FC Skills collection (Research Methods & Academic Writing department).

    The same file is in 1 other repository

  • Alterlab rma survey builder

    prone-dc302/AlterLab-FC-Skills/skills/rma/alterlab-rma-survey-builder Skill

    0★ repo

    This skill should be used when the user asks about "survey design", "questionnaire construction", "Likert scale", "question wording", "response bias", "survey tool", "Google Forms", "Qualtrics", "SurveyMonkey", "Typeform", "pilot testing", "survey distribution", "act as a survey builder", "survey builder mode", "survey instrument", "closed-ended questions", "open-ended questions", "rating scale", "semantic differential", "survey flow", "skip logic", "branching logic", "response rate", "survey fatigue", "questionnaire validation", "pre-test survey", "online survey", "survey analysis", "Cronbach's alpha", "factor analysis", "survey consent form", "demographic questions", or needs expertise in designing, building, distributing, and validating survey instruments. Part of the AlterLab FC Skills collection (Research Methods & Academic Writing department).

    The same file is in 1 other repository

  • Flow

    supermodo/skills/skills/flow Skill

    0★ repo

    Orchestrates the full supermodo development pipeline end-to-end for one task, running each stage in its own subagent so the main context stays small. Eight stages: librarian task intake (grilled), work implementation, optional hunt bug audit, tdd fixes for any bugs found, a mandatory tests gate (suite green + coverage target), refactor, a mandatory post-refactor verify gate, a final librarian docs pass, and commit. Supports entering at a later stage (--from work|hunt|tests|refactor|librarian|commit) and three job sources: an existing docs/work triad, a backlog entry, or a completely new task — with a context-aware "next job" suggestion when none is named. Use when the user wants to run the whole pipeline, "take this task from spec to commit", orchestrate a feature end-to-end, run the full flow (or the flow from a given stage), or drive a task through the complete dev-to-commit process — anything that means coordinating grill → work → hunt → tdd → tests → refactor → librarian → commit rather than a single stage.

  • Tdd

    supermodo/skills/skills/tdd Skill

    0★ repo

    Test-driven work in two modes. Default: real Test-Driven Development — red-green-refactor, one failing test at a time, used while implementing features (and by the work skill). With --debug: test-first debugging — generate all plausible root-cause hypotheses, write tests to validate each before touching production code, fix based on which tests fail, then sweep the codebase for the same pattern. Use for 'tdd', 'test-driven', 'write the test first', implementing with tests leading — and with --debug whenever the user reports a bug, unexpected behavior, or failed fix attempts and the root cause is unclear.

  • 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".

  • 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.

  • 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.

  • Tests

    theinterneti/TTA.dev/.claude/skills/generated/tests Skill

    0★ repo

    Tests area in TTA.dev (session and related). 224 symbols | 25 files | Cohesion: 77%

  • 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.

  • Fix bug

    gabriel-f-santos/coding-agents/skills/fix-bug Skill

    no license0★ repo

    Fix a bug the disciplined way — reproduce, write a FAILING regression test, then fix until green. Use when the user reports a bug or asks to fix/debug something — "tem um bug", "corrige esse erro", "fix this bug", "isso deveria retornar X mas retorna Y", "debug isso", "não está funcionando", "reproduz e corrige". Enforces TDD red-green for bugs: reproduce deterministically, write a regression test that asserts the CORRECT behavior and fails on the current code (confirm Red), make the smallest root-cause fix, confirm the test passes (Green), then run the full suite so nothing regressed. Hard rule: never declare it fixed without a test that reproduced the bug now passing. Runs the tests when a runner exists, else writes the test + fix and flags it unverified. Do not use to add a new feature (use implement-phase) or for pure code review (use review-*).

  • Qa tester

    karim-bhalwani/agent-skills-collection/skills/qa-tester Skill

    0★ repo

    Expert in automated QA testing, E2E test automation, visual regression testing, and intelligent test generation. Use when building automated test suites, validating user workflows, testing external integrations, setting up test infrastructure, or implementing AI-powered test discovery.

  • Interswitch testing

    rexedge/interswitch/skills/interswitch-testing Skill

    no license0★ repo

    Interswitch Testing — test credentials, test cards, sandbox URLs, environment switching, and testing strategies for all Interswitch APIs. Use this skill whenever testing Interswitch integrations, using test card numbers, configuring the sandbox environment, verifying payment flows with test data, or debugging test transactions. Also use when you see references to test credentials, sk_test_, sandbox URLs, test card numbers (5061050254756707864, 4000000000002503), or QA environments.

  • Test driven development

    songsunny00/MySkills/CoderSkills/.agents/skills/test-driven-development Skill

    no license0★ repo

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

    The same file is in 33 other repositories

  • Webapp testing

    songsunny00/MySkills/CoderSkills/.agents/skills/webapp-testing Skill

    no license0★ repo

    Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

    The same file is in 45 other repositories

  • Browser proxy

    luis2404123/birdproxies-skills/browser-proxy Skill

    0★ repo

    Configure proxy settings for browser automation with Playwright, Puppeteer, Selenium, and the OpenClaw browser tool. Route browser traffic through residential proxies for stealth scraping.

  • Architecture

    jovd83/junit5-skill/architecture Skill

    0★ repo

    Use when Codex needs to shape or refactor JUnit 5 suite architecture, test package structure, naming, fixture ownership, reuse patterns, or boundaries between component, integration, and service tests.

  • Tests

    jovd83/junit5-skill/documentation/tests Skill

    0★ repo

    Use when Codex needs to document JUnit 5 automation code with clear scenario intent, suite purpose, traceability, or maintainable human-readable explanations.

  • Qa

    javalenciacai/develop-skills/.agents/skills/qa Skill

    0★ repo

    Quality Assurance. Designs and executes tests, validates acceptance criteria, reports bugs. Works with Vitest (frontend) and Jest (backend). Reports to QAL. Use when: (1) Writing or executing test cases, (2) Test automation with Vitest, Jest or Playwright, (3) Validating acceptance criteria, (4) Bug reporting, tracking or regression testing, (5) End-to-end testing or integration testing, (6) Test coverage analysis or quality metrics, (7) Functional testing or smoke testing.

  • Qal

    javalenciacai/develop-skills/.agents/skills/qal Skill

    0★ repo

    Quality strategy orchestrator. QA Lead coordinates QA and SecOps for functional testing, automation and security. Ensures product quality and defines testing strategies. Reports to CTO. Use when: (1) Defining quality assurance strategy or test plans, (2) Functional testing, test automation or bug tracking needed, (3) Security audits, vulnerability assessments or DevSecOps required, (4) Test coverage analysis or quality metrics reporting, (5) Compliance validation or security policies, (6) Incident management or post-mortems for quality issues, (7) Coordinating between QA testing and security operations.

  • Ab test setup

    planifest/planifest-framework/planifest-framework/external-skills/ab-test-setup Skill

    0★ repo

    When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics-tracking. For page-level conversion optimization, see page-cro.

  • Ab testing

    planifest/planifest-framework/planifest-framework/external-skills/ab-testing Skill

    0★ repo

    Controlled online experiment workflow for product changes with causal inference, randomization integrity checks, and pre-registered decision criteria. Trigger when ship/no-ship decisions require causal evidence under uncertainty and KPI trade-offs must be quantified. Do not use for feature-flag rollout policy without experiment design, deterministic functional verification, or observability-only analysis.

  • Api contract testing

    planifest/planifest-framework/planifest-framework/external-skills/api-contract-testing Skill

    0★ repo

    Consumer-provider contract testing and release-gate design for compatibility matrices, contract assertions, and CI blocking rules across versions and transports. Trigger when API contract diffs are detected but compatibility evidence is missing or stale (contract test pass, consumer-impact mapping, or compatibility matrix update), or when multiple consumers, versions, or transports must be protected by automated gates. Do not use for first-pass API interface design.

  • Api testing observability api mock

    planifest/planifest-framework/planifest-framework/external-skills/api-testing-observability-api-mock Skill

    0★ repo

    You are an API mocking expert specializing in realistic mock services for development, testing, and demos. Design mocks that simulate real API behavior and enable parallel development.

    The same file is in 7 other repositories

  • Browse

    planifest/planifest-framework/planifest-framework/external-skills/browse Skill

    0★ 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)

  • Browser testing with devtools

    planifest/planifest-framework/planifest-framework/external-skills/browser-testing-with-devtools Skill

    0★ repo

    Tests in real browsers. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data via Chrome DevTools MCP.

    The same file is in 5 other repositories

  • Cloud penetration testing

    planifest/planifest-framework/planifest-framework/external-skills/cloud-penetration-testing Skill

    0★ repo

    Conduct comprehensive security assessments of cloud infrastructure across Microsoft Azure, Amazon Web Services (AWS), and Google Cloud Platform (GCP).

    The same file is in 1 other repository

  • Continuous discovery

    planifest/planifest-framework/planifest-framework/external-skills/continuous-discovery Skill

    0★ repo

    Build a weekly cadence of customer touchpoints using Opportunity Solution Trees, assumption mapping, and interview snapshots. Use when the user mentions "continuous discovery", "opportunity solution tree", "weekly interviews", "assumption testing", "discovery habits", "product trio", or "outcome-based roadmap". Also trigger when setting up regular customer feedback loops, prioritizing which experiments to run, or connecting discovery insights to delivery work. Covers experience mapping, co-creation, and prioritizing opportunities. For interview technique, see mom-test. For team structure, see inspired-product.

  • Jest testing workflow

    planifest/planifest-framework/planifest-framework/external-skills/jest-testing-workflow Skill

    0★ repo

    Jest verification workflow for JavaScript/TypeScript codebases with deterministic tests, explicit mock boundaries, and actionable CI evidence. Use when JS/TS changes need executable Jest evidence before merge; do not use for browser-level E2E or language-agnostic policy design.

  • K6 load testing

    planifest/planifest-framework/planifest-framework/external-skills/k6-load-testing Skill

    0★ repo

    Comprehensive k6 load testing skill for API, browser, and scalability testing. Write realistic load scenarios, analyze results, and integrate with CI/CD.

    The same file is in 6 other repositories

  • Mom test

    planifest/planifest-framework/planifest-framework/external-skills/mom-test Skill

    0★ repo

    Talk to customers without leading them using Mom Test rules: discuss their life not your idea, ask about specifics in the past, and talk less. Use when the user mentions "customer interviews", "validate my idea", "users say they want it but dont buy", "leading questions", "The Mom Test", "customer feedback bias", or "interview script". Also trigger when preparing user research questions, interpreting ambiguous customer feedback, or designing customer discovery processes that avoid false positives. Covers commitment and advancement, avoiding compliments, and extracting signal from noise. For product-market fit, see jobs-to-be-done. For rapid prototype testing, see design-sprint.

  • Performance load testing

    planifest/planifest-framework/planifest-framework/external-skills/performance-load-testing Skill

    0★ repo

    Performance load testing workflow for realistic workload simulation, bottleneck detection, and saturation behavior analysis. Use when systems need throughput/latency validation before rollout; do not use for non-performance functional acceptance decisions.

  • Plan eng review

    planifest/planifest-framework/planifest-framework/external-skills/plan-eng-review Skill

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

  • Playwright

    planifest/planifest-framework/planifest-framework/external-skills/playwright Skill

    0★ repo

    Playwright browser verification workflow for user-journey evidence with deterministic replay artifacts. Use when web flows require executable browser evidence (trace/screenshot/replay logs) before merge or release; do not use for pure unit/API-only checks.

  • Pytest workflow

    planifest/planifest-framework/planifest-framework/external-skills/pytest-workflow Skill

    0★ repo

    Pytest verification workflow for Python changes with deterministic fixtures, explicit case strategy, and CI-ready evidence. Use when Python modules need executable pytest evidence before merge; do not use for browser-level E2E or non-Python test tooling decisions.

  • Qa only

    planifest/planifest-framework/planifest-framework/external-skills/qa-only Skill

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

  • Test automator

    planifest/planifest-framework/planifest-framework/external-skills/test-automator Skill

    0★ repo

    Master AI-powered test automation with modern frameworks, self-healing tests, and comprehensive quality engineering. Build scalable testing strategies with advanced CI/CD integration.

    The same file is in 4 other repositories

  • Test data generation

    planifest/planifest-framework/planifest-framework/external-skills/test-data-generation Skill

    0★ repo

    Generate realistic, consistent test data using factories, fixtures, and fake data libraries. Use for test data, fixtures, mock data, faker, test builders, and seed data generation.

    The same file is in 1 other repository

  • Test driven development

    planifest/planifest-framework/planifest-framework/external-skills/test-driven-development Skill

    0★ repo

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

    The same file is in 33 other repositories

  • Testing bdd

    planifest/planifest-framework/planifest-framework/external-skills/testing-bdd Skill

    0★ repo

    Behavior-driven scenario design for shared business language and executable acceptance evidence. Use when teams must align on Given-When-Then scenarios before implementation sign-off or release; do not use for performance benchmarking or deployment policy design.

  • Testing contract

    planifest/planifest-framework/planifest-framework/external-skills/testing-contract Skill

    0★ repo

    Provider-consumer compatibility testing for service interface changes. Use when APIs or event schemas evolve and executable contract checks must guard compatibility before release; do not use for UI-only validation or architecture topology decisions.

  • Testing e2e

    planifest/planifest-framework/planifest-framework/external-skills/testing-e2e Skill

    0★ repo

    End-to-end test planning for critical user journeys across integrated systems. Use when release confidence depends on browser/API/dependency behavior as one flow; do not use for isolated unit behavior or pure contract checks.

  • Testing integration

    planifest/planifest-framework/planifest-framework/external-skills/testing-integration Skill

    0★ repo

    Integration-boundary testing for component and service collaboration correctness. Use when modules interact via APIs, queues, databases, or adapters and boundary behavior must be verified; do not use for full UI journey validation or pure unit isolation work.

  • Testing mutation

    planifest/planifest-framework/planifest-framework/external-skills/testing-mutation Skill

    0★ repo

    Mutation-testing workflow for exposing weak assertions and missing behavioral checks. Use when tests pass but confidence is low and objective robustness evidence is needed; do not use before baseline tests exist.

  • Testing property based

    planifest/planifest-framework/planifest-framework/external-skills/testing-property-based Skill

    0★ repo

    Property-based testing workflow for invariant validation over broad input spaces. Use when correctness depends on rules that must hold across many generated inputs; do not use for narrow deterministic examples only.

  • Testing regression strategy

    planifest/planifest-framework/planifest-framework/external-skills/testing-regression-strategy Skill

    0★ repo

    Risk-based regression suite curation for release gating under time and budget limits. Use when teams must decide what runs always versus conditionally by impact and risk; do not use for implementing a single test type in isolation.

  • Testing tdd

    planifest/planifest-framework/planifest-framework/external-skills/testing-tdd Skill

    0★ repo

    Red-green-refactor workflow for test-first implementation feedback loops. Use when behavior and design must evolve safely through small increments backed by failing-then-passing tests; do not use for post-hoc test backfilling only.

  • Testing unit

    planifest/planifest-framework/planifest-framework/external-skills/testing-unit Skill

    0★ repo

    Deterministic unit-test strategy for isolated logic and fast feedback. Use when core logic branches, error paths, and edge conditions need low-latency regression evidence with controlled dependencies; do not use for browser-flow or cross-service compatibility validation.

  • Unit testing test generate

    planifest/planifest-framework/planifest-framework/external-skills/unit-testing-test-generate Skill

    0★ repo

    Generate comprehensive, maintainable unit tests across languages with strong coverage and edge case focus.

    The same file is in 5 other repositories