Wreck It

Full 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

Testing & QA

Install

skills CLI (Claude Code, Cursor, Codex and more)

npx skills add miyannishar/wreck-it --skill wreck-it

Manual install

git clone --depth 1 https://github.com/miyannishar/wreck-it.git /tmp/wreck-it
mkdir -p ~/.claude/skills
cp -r /tmp/wreck-it/skills/wreck-it ~/.claude/skills/wreck-it

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# wreck-it: Wreck your app before your users do

`WRECK` below means `npx @miyanishar/wreck-it`. The CLI does the deterministic work (setup, discovery, sweeps, fuzzing, page speed, load, findings, score, report, tests). You drive the browser through Playwright MCP, play the personas, judge what's a bug and trace it to code.

Report only. **Don't fix bugs** during a run unless the user asks after the report.

## Rules (always)

- **Local only.** The CLI refuses non-local targets. Pass `--i-own-this` only when the user says they own a remote one.
- **Fake data only.** Test accounts, fake names, never real personal or payment data. Name what you create `wreck-it …`, and log it: `WRECK run created "<what>" --by <persona>` (the report lists it for cleanup).
- **Ask before writing.** Preflight's `safety.ask` lists the questions: a hosted (often production) database, live Stripe keys, email without a readable inbox, paid AI/SMS calls. Ask them all in **one** message before the normal-user pass, and record each "yes" in `.wreck-it/config.json` (`allowRemoteDb`, `testEmail`, `allowSideEffects`). If the database is production, offer to stop so they can point the app at a dev project.
- **Money and messages.** Pay only with Stripe test keys (card `4242 4242 4242 4242`); with live keys stop at the payment step. Trigger AI/SMS/email actions at most 2–3 times per flow unless allowed. `fuzz` and `load` skip those endpoints themselves.

Read the full skill on GitHub

Details

Skill name: wreck-it
Repository: miyannishar/wreck-it
Path: skills/wreck-it/SKILL.md
License: MIT
Repo updated: 25 October 2026
Listed in: karanb192/awesome-claude-skills

FAQ

What does the Wreck It skill do?

How do I install the Wreck It skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add miyannishar/wreck-it --skill wreck-it. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Related skills

Analyzing Test Coverage

jeremylongshore/claude-code-plugins-plus-skills

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

Testing & QA

Watch

igamingsychov/watch-igaming

Смотрит любое видео - по ссылке (видеохостинг, запись экрана или встречи, прямой mp4) или локальный файл (.mov/.mp4) - не только читает транскрипт, но и видит, что на экране. Кадры берёт по сменам сцен (ffmpeg scene detection), а не по таймеру, поэтому не пропускает графику, демо, монтаж и b-roll. Звук: субтитры через yt-dlp, fallback - локальная расшифровка речи. Результат - разбор или таблица в нужном формате: QA-таблица, сравнение конкурентов, UX-аудит, протокол созвона, конспект лекции. Используй, когда пользователь пишет /watch <url> или просит «посмотри это видео», «разбери ролик/созвон/

Testing & QAIn 1 list

Automating Api Testing

jeremylongshore/claude-code-plugins-plus-skills

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

Testing & QA

Test Checklist

Ifeanyiejindu/qarunbook

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

Testing & QAIn 1 list

Automating Mobile App Testing

jeremylongshore/claude-code-plugins-plus-skills

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

Testing & QA

Prove It Ran

agentkitco/agentkit-dev-skills

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

Testing & QAIn 1 list

Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.