#SkillRepo stars
- 961QA RunbookIfeanyiejindu/qarunbookRun a QA sweep for any app against the qa-runbook MCP — establish what is under test, create real test accounts, drive web and mobile, verify fixes, and record results with evidence. Use when asked to run QA, test a section, retest a check, clear a QA backlog, or verify a fix against a runbook.
- 962Test ChecklistIfeanyiejindu/qarunbookBuild a complete QA test plan for an app — every module, feature and user journey, across each platform it runs on. Use when asked for a test plan, QA checklist, test cases, regression suite, or "what should we test", or when preparing an app for QA, a release or a demo. Writes the plan, puts it into qarunbook (creating the app, or adding to it), then offers to start testing it straight away.
- 963Analyzing Test Coveragejeremylongshore/claude-code-plugins-plus-skillsThis skill analyzes code coverage metrics to identify untested code and generate comprehensive coverage reports. It is triggered when the user requests analysis of code coverage, identification of coverage gaps, or generation of coverage reports. The skill is best used to improve code quality by ensuring adequate test coverage and identifying areas for improvement. Use trigger terms like "analyze coverage", "code coverage report", "untested code", or the shortcut "cov".
- 964Automating Api Testingjeremylongshore/claude-code-plugins-plus-skillsThis skill automates API endpoint testing, including request generation, validation, and comprehensive test coverage for REST and GraphQL APIs. It is used when the user requests API testing, contract testing, or validation against OpenAPI specifications. The skill analyzes API endpoints and generates test suites covering CRUD operations, authentication flows, and security aspects. It also validates response status codes, headers, and body structure. Use this skill when the user mentions "API testing", "REST API tests", "GraphQL API tests", "contract tests", or "OpenAPI validation".
- 965Automating Mobile App Testingjeremylongshore/claude-code-plugins-plus-skillsThis skill enables automated testing of mobile applications on iOS and Android platforms using frameworks like Appium, Detox, XCUITest, and Espresso. It generates end-to-end tests, sets up page object models, and handles platform-specific elements. Use this skill when the user requests mobile app testing, test automation for iOS or Android, or needs assistance with setting up device farms and simulators. The skill is triggered by terms like "mobile testing", "appium", "detox", "xcuitest", "espresso", "android test", "ios test".
- 966Conducting Browser Compatibility Testsjeremylongshore/claude-code-plugins-plus-skillsThis skill enables cross-browser compatibility testing for web applications using BrowserStack, Selenium Grid, or Playwright. It tests across Chrome, Firefox, Safari, and Edge, identifying browser-specific bugs and ensuring consistent functionality. It is used when a user requests to "test browser compatibility", "run cross-browser tests", or uses the `/browser-test` or `/bt` command to assess web application behavior across different browsers and devices. The skill generates a report detailing compatibility issues and screenshots for visual verification.
- 967Conducting Chaos Engineeringjeremylongshore/claude-code-plugins-plus-skillsThis skill enables Claude to design and execute chaos engineering experiments to test system resilience. It is used when the user requests help with failure injection, latency simulation, resource exhaustion testing, or resilience validation. The skill is triggered by discussions of chaos experiments (GameDays), failure injection strategies, resilience testing, and validation of recovery mechanisms like circuit breakers and retry logic. It leverages tools like Chaos Mesh, Gremlin, Toxiproxy, and AWS FIS to simulate real-world failures and assess system behavior.
- 968Generating End To End Testsjeremylongshore/claude-code-plugins-plus-skillsThis skill enables Claude to generate end-to-end (E2E) tests for web applications. It leverages Playwright, Cypress, or Selenium to automate browser interactions and validate user workflows. Use this skill when the user requests to "create E2E tests", "generate end-to-end tests", or asks for help with "browser-based testing". The skill is particularly useful for testing user registration, login flows, shopping cart functionality, and other multi-step processes within a web application. It supports cross-browser testing and can be used to verify the responsiveness of web applications on differe
- 969Generating Test Datajeremylongshore/claude-code-plugins-plus-skillsThis skill enables Claude to generate realistic test data for software development. It uses the test-data-generator plugin to create users, products, orders, and custom schemas for comprehensive testing. Use this skill when you need to populate databases, simulate user behavior, or create fixtures for automated tests. Trigger phrases include "generate test data", "create fake users", "populate database", "generate product data", "create test orders", or "generate data based on schema". This skill is especially useful for populating testing environments or creating sample data for demonstration
- 970Generating Test Doublesjeremylongshore/claude-code-plugins-plus-skillsThis skill uses the test-doubles-generator plugin to automatically create mocks, stubs, spies, and fakes for unit testing. It analyzes dependencies in the code and generates appropriate test doubles based on the chosen testing framework, such as Jest, Sinon, or others. Use this skill when you need to generate test doubles, mocks, stubs, spies, or fakes to isolate units of code during testing. Trigger this skill by requesting test double generation or using the `/gen-doubles` or `/gd` command.
- 971Generating Test Reportsjeremylongshore/claude-code-plugins-plus-skillsThis skill generates comprehensive test reports with coverage metrics, trends, and stakeholder-friendly formats (HTML, PDF, JSON). It aggregates test results from various frameworks, calculates key metrics (coverage, pass rate, duration), and performs trend analysis. Use this skill when the user requests a test report, coverage analysis, failure analysis, or historical comparisons of test runs. Trigger terms include "test report", "coverage report", "testing trends", "failure analysis", and "historical test data".
- 972Generating Unit Testsjeremylongshore/claude-code-plugins-plus-skillsThis skill enables Claude to automatically generate comprehensive unit tests from source code. It is triggered when the user requests unit tests, test cases, or test suites for specific files or code snippets. The skill supports multiple testing frameworks including Jest, pytest, JUnit, and others, intelligently detecting the appropriate framework or using one specified by the user. Use this skill when the user asks to "generate tests", "create unit tests", or uses the shortcut "gut" followed by a file path.
- 973Managing Database Testingjeremylongshore/claude-code-plugins-plus-skillsThis skill manages database testing by generating test data, wrapping tests in transactions, and validating database schemas. It is used to create robust and reliable database interactions. Claude uses this skill when the user requests database testing utilities, including test data generation, transaction management, schema validation, or migration testing. Trigger this skill by mentioning "database testing," "test data factories," "transaction rollback," "schema validation," or using the `/db-test` or `/dbt` commands.
- 974Managing Snapshot Testsjeremylongshore/claude-code-plugins-plus-skillsThis skill enables Claude to manage and update snapshot tests using intelligent diff analysis and selective updates. It is triggered when the user asks to analyze snapshot failures, update snapshots, or manage snapshot tests in general. It helps distinguish intentional changes from regressions, selectively update snapshots, and validate snapshot integrity. Use this when the user mentions "snapshot tests", "update snapshots", "snapshot failures", or requests to run "/snapshot-manager" or "/sm". It supports Jest, Vitest, Playwright, and Storybook frameworks.
- 975Managing Test Environmentsjeremylongshore/claude-code-plugins-plus-skillsThis skill enables Claude to manage isolated test environments using Docker Compose, Testcontainers, and environment variables. It is used to create consistent, reproducible testing environments for software projects. Claude should use this skill when the user needs to set up a test environment with specific configurations, manage Docker Compose files for test infrastructure, set up programmatic container management with Testcontainers, manage environment variables for tests, or ensure cleanup after tests. Trigger terms include "test environment", "docker compose", "testcontainers", "environme
- 976Orchestrating Test Workflowsjeremylongshore/claude-code-plugins-plus-skillsThis skill enables Claude to orchestrate complex test workflows using the test-orchestrator plugin. It allows Claude to define test execution graphs with dependencies, execute tests in parallel, and intelligently select tests to run based on code changes. Use this skill when a user requests test orchestration, dependency management for tests, parallel test execution, smart test selection, or CI/CD integration for testing. Trigger terms include "orchestrate tests", "test workflow", "parallel testing", "smart test selection", "test dependencies", and "/orchestrate".
- 977Performance Testingjeremylongshore/claude-code-plugins-plus-skillsThis skill enables Claude to design, execute, and analyze performance tests using the performance-test-suite plugin. It is activated when the user requests load testing, stress testing, spike testing, or endurance testing, and when discussing performance metrics such as response time, throughput, and error rates. It identifies performance bottlenecks related to CPU, memory, database, or network issues. The plugin provides comprehensive reporting, including percentiles, graphs, and recommendations.
- 978Performing Visual Regression Testingjeremylongshore/claude-code-plugins-plus-skillsThis skill enables Claude to execute visual regression tests using tools like Percy, Chromatic, and BackstopJS. It captures screenshots, compares them against baselines, and analyzes visual differences to identify unintended UI changes. Use this skill when the user requests visual testing, UI change verification, or regression testing for a web application or component. Trigger phrases include "visual test," "UI regression," "check visual changes," or "/visual-test".
- 979Playwright Browser AutomationModel-invoked browser automation for web testing using Playwright. Automate browser interactions and validate web applications.
- 980Running Integration Testsjeremylongshore/claude-code-plugins-plus-skillsThis skill enables Claude to run and manage integration test suites. It automates environment setup, database seeding, service orchestration, and cleanup. Use this skill when the user asks to "run integration tests", "execute integration tests", or any command that implies running integration tests for a project, including specifying particular test suites or options like code coverage. It is triggered by phrases such as "/run-integration", "/rit", or requests mentioning "integration tests". The plugin handles database creation, migrations, seeding, and dependent service management.
- 981Running Load Testsjeremylongshore/claude-code-plugins-plus-skillsThis skill enables Claude to create and execute load tests for performance validation. It is designed to generate load test scripts using tools like k6, JMeter, and Artillery, based on specified test scenarios. Use this skill when the user requests to create a "load test", conduct "performance testing", validate "application performance", or needs a "stress test" to identify breaking points in the application. The skill helps define performance thresholds and provides execution instructions.
- 982Running Mutation Testsjeremylongshore/claude-code-plugins-plus-skillsThis skill enables Claude to validate test suite quality by performing mutation testing. It is triggered when the user asks to run mutation tests, analyze test effectiveness, or improve test coverage. The skill introduces code mutations, runs tests against the mutated code, and reports on the "survival rate" of the mutations, indicating the effectiveness of the test suite. Use this skill when the user requests to assess the quality of their tests using mutation testing techniques. Specific trigger terms include "mutation testing", "test effectiveness", "mutation score", and "surviving mutants"
- 983Running Smoke Testsjeremylongshore/claude-code-plugins-plus-skillsThis skill runs smoke tests to verify critical application functionality. It executes pre-defined test suites that check system health, authentication, core features, and external integrations. Use this skill after deployments, upgrades, or significant configuration changes to ensure the application is operational. Trigger this skill using the terms "smoke test" or "st".
- 984Splitting Datasetsjeremylongshore/claude-code-plugins-plus-skillsThis skill enables Claude to split datasets into training, validation, and testing sets. It is useful when preparing data for machine learning model development. Use this skill when the user requests to split a dataset, create train-test splits, or needs data partitioning for model training. The skill is triggered by terms like "split dataset," "train-test split," "validation set," or "data partitioning.
- 985Test FixingDetects failing tests and proposes fixes. Automatically identify test failures and suggest solutions.
- 986Testing Load Balancersjeremylongshore/claude-code-plugins-plus-skillsThis skill enables Claude to test load balancing strategies. It validates traffic distribution across backend servers, tests failover scenarios when servers become unavailable, verifies sticky sessions, and assesses health check functionality. Use this skill when the user asks to "test load balancer", "validate traffic distribution", "test failover", "verify sticky sessions", or "test health checks". It is specifically designed for testing load balancing configurations using the `load-balancer-tester` plugin.
- 987Tracking Regression Testsjeremylongshore/claude-code-plugins-plus-skillsThis skill enables Claude to track and run regression tests, ensuring new changes don't break existing functionality. It is triggered when the user asks to "track regression", "run regression tests", or uses the shortcut "reg". The skill helps in maintaining code stability by identifying critical tests, automating their execution, and analyzing the impact of changes. It also provides insights into test history and identifies flaky tests. The skill uses the `regression-test-tracker` plugin.
- 988Wreck Chaosmiyannishar/wreck-itChaos-test a running local web app as the chaos-monkey persona, using a page sweep, an API fuzzer (plus Schemathesis when there's an OpenAPI spec), hostile form inputs, double-submits, back/forward/refresh mid-flow, multiple tabs, offline/slow/500-injected network, expired or tampered sessions, an axe-core scan and keyboard-only navigation. Records reproducible bugs with wreck-it. Use as stage 6 of a wreck-it run, or when the user asks to "break my forms", "chaos test", "try weird inputs", "test offline", or "check accessibility".
- 989Wreck Exploremiyannishar/wreck-itExplore a running local web app through Playwright MCP as a normal user (every core flow plus data-integrity checks) and then in character as each persona from .wreck-it/personas.md, recording reproducible bugs with wreck-it. Use as stages 4–5 of a wreck-it run, or when the user asks to "click through my app like a user", "test the happy paths", "try my app as a beginner", or "check my core flows".
- 990Wreck Itmiyannishar/wreck-itFull wreck-it run against a locally running web app. It tests like normal users, ICP personas, rushed beginners, chaos monkeys and traffic spikes, then writes a scored bug report with source file:line and regression Playwright tests. Use when the user says "wreck my app", "wreck it", "test my app like a user", "find bugs before launch", "is my app ready to ship", or asks for a readiness score. Also for one feature, such as "test the checkout", "just test signup", "check the coupon flow" (a focused run). For a single stage ("just stress test my API", "only check accessibility"), use the matchin
- 991Wreck Loadmiyannishar/wreck-itPage speed and load testing for a local web app with the wreck-it CLI. It measures each page with Lighthouse on a simulated phone (LCP, CLS, TBT), diagnoses slow pages with Chrome DevTools performance traces when available, runs ramp, spike and soak load profiles (p50/p90/p99 latency, error rate, breaking point, memory trend), then traces slow endpoints to causes such as N+1 queries, missing indexes or blocking work. Use as stage 7 of a wreck-it run, or when the user asks to "stress test my API", "load test", "how many users can my app handle", "find slow endpoints", "check page speed", or "ru
- 992Wreck Personasmiyannishar/wreck-itDerive realistic user personas (the app's ideal customers plus built-in normal-user, rushed-beginner and chaos-monkey) and their missions for wreck-it testing, saved to .wreck-it/personas.md. Use as stage 3 of a wreck-it run, or when the user asks "who would use my app", "make test personas", or wants to edit the personas used for testing.
- 993Smokedanybgoode/golden-frijolesVerifies real, rendered behavior on this project's frontend (local/preview/staging/prod, unauthed or authed) via a real headless-Chromium Playwright browser — the DEFAULT way to check "does this render correctly / does this look right / is this actually live" for any coding agent, not just Claude Code. Use when asked to "smoke test", "verify the live/prod page", "check if X actually rendered", "run a browser smoke", "does this look right on preview", "verify an authed role's flow", or as a post-merge/pre-PR verification step. Wraps the project's scripts/live-smoke.mjs — a real screenshot + JSO
- 994Prove It Ranagentkitco/agentkit-dev-skillsVerify that tests, builds and checks actually ran and exercised the changed code, before claiming a task is done. Use before reporting completion, or when asked to prove tests ran or verify a fix.