Test Checklist

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 & QA

Install

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

npx skills add Ifeanyiejindu/qarunbook --skill test-checklist

Manual install

git clone --depth 1 https://github.com/Ifeanyiejindu/qarunbook.git /tmp/qarunbook
mkdir -p ~/.claude/skills
cp -r /tmp/qarunbook/plugins/qarunbook/skills/test-checklist ~/.claude/skills/test-checklist

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

From the SKILL.md

# Building a test checklist

The goal is a document a **non-technical tester** can work top to bottom, where
finishing it means the app has genuinely been exercised. A missing journey is a
missed bug.

## Derive it from the code, never from memory

Walk every codebase the product ships from — backend, web, each mobile app — and
build the module list from what is actually there:

- **Backend**: the modules directory is the authoritative feature list. Controllers
give the real endpoints, and therefore the real capabilities.
- **Web**: the routes give the surfaces; look for separate mobile components, since
a responsive app and a purpose-built mobile view are different code.
- **Mobile**: the modules/views directories.

A feature that exists on one platform and not another is exactly the kind of gap
the document must **expose**, not paper over. List those up front as known gaps so
testers do not report deliberate differences as defects.

If the product has an existing plan, read it first and extend rather than replace.

**The code isn't on this computer?** When the app's GitHub repositories are connected in qarunbook,
read them through it: `code_sources` names them (and which platforms each builds), `repo_files`
lists their source files, and `read_repo_file` reads one. Walk them exactly as you would a local
checkout — routes, screens, modules, controllers — and build the plan from what is there.

## Structure

**Part → Section → Journey**, with a result column per platform.

Read the full skill on GitHub

Details

Skill name: test-checklist
Repository: Ifeanyiejindu/qarunbook
Path: plugins/qarunbook/skills/test-checklist/SKILL.md
License: MIT
Repo updated: 25 October 2026
Listed in: karanb192/awesome-claude-skills

FAQ

What does the Test Checklist skill do?

How do I install the Test Checklist skill?

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

Related skills

Watch

igamingsychov/watch-igaming

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

Testing & QAIn 1 list

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

Wreck It

miyannishar/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 & QAIn 1 list

Keyboard Shortcuts

nparashar150/claude-keyboard-shortcuts

Audit a web app for missing keyboard shortcuts and implement them end to end: a command registry, context-scoped bindings, a command palette, visible kbd hints, a ? help sheet, invariant tests, and WCAG 2.1.4 compliance. Use whenever the user mentions keyboard shortcuts, hotkeys, keybindings, a command palette, Cmd+K, power-user features, or making an app feel fast, and also when building or reviewing any list, table, modal, form, or editor UI where shortcuts and keyboard access obviously belong even if the user never says the word shortcut.

Testing & QAIn 1 list

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

Grill

mtangoz/grill

Grill a decision, plan or forecast. An outside AI judge, a model from a different company than Claude, argues the strongest case for and against it, names the cheapest test that would settle each challenge, and gives a verdict. Use when the user says grill, stress-test, pressure-test, poke holes in, red-team or challenge something they decided or plan to decide, when the weekly review marks a decision for grilling, or when they say look back or paste a decision record to score.

Testing & QAIn 1 list

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