🚀 Casely — AI QA Test Case Generator

Attach your requirements and approve one plan. Casely returns a TestRail-ready Excel file.
Free, open-source QA skill for Claude Code, claude.ai and the Claude desktop app.

License: MIT Version Stars Casely Web

Watch it work

https://github.com/user-attachments/assets/57f086c4-ec92-4a60-bc58-a00cc9757ee0

The problem

You were hired to find bugs, and 40% of your week goes into writing test cases.

Requirements land as unstructured PDFs. Projects rename the columns, so you remap them each sprint. One module takes two days to document, and then the TestRail import fails because the headers don't match.

How it works

Attach your files and say what you need:

"Here are the requirements for the Payments module and two example test cases my team writes. Give me test cases for the refund flow."

Casely runs five phases in that same conversation:

Phase What happens
Intake Reads your PDF, DOCX or XLSX attachments. No parser, no OCR setup
Style guide Copies the column structure and tone from your example file
Test plan Proposes coverage, flags holes in the spec, then waits for your OK
Generate Writes the cases using boundary values, decision tables and negative paths
Export Builds one Excel file your TMS imports in a single pass

You only get interrupted once, at the plan. Adjust the scope, drop a module, add negative cases, or say "go".

Install

Claude Code

bunx skills add JohnWayneeee/casely-qa-skill
# or: npx skills@latest add JohnWayneeee/casely-qa-skill

claude.ai and Claude desktop

  1. Get the upload archive, already zipped with casely/ at its root: download casely-v2.1.0.zip from the latest release.

    Building it yourself works too — just not GitHub's own "Download ZIP" button, which wraps everything in casely-qa-skill-main/skill/casely/ instead of putting SKILL.md at the archive root, which is what claude.ai requires:

    git clone https://github.com/JohnWayneeee/casely-qa-skill.git
cd casely-qa-skill/skill && zip -r casely.zip casely

  2. On claude.ai, open Settings → Capabilities, turn on Code execution if it isn't already, then go to Skills → Create skill and upload the zip.

  3. The Claude desktop app uses the same account, so the skill is available there too — nothing to install separately.

  4. Start a chat, attach your files, describe what you need.

Nothing to install locally. The export step uses openpyxl, which already ships inside Claude's code execution environment. Custom skills are private to your account (Pro, Max, Team, or Enterprise plan required) and won't sync to a Claude Code install — set that up separately with the command above.

Pick Opus. The plan phase decides what gets tested at all: which boundaries matter, which conditions combine, which requirement is too vague to test. Smaller models write acceptable cases from a plan they were handed, and miss the holes in the spec.

What you get

  • exports/all_test_cases.xlsx with one row per case and your own column headers. Import it once instead of forty times.
  • results/*.md, one file per case, so you can review or version-control them separately.
  • A list of holes in the spec: contradictions, untestable wording ("should be fast"), and error paths the requirements never mention.

The export refuses to write a file it cannot read faithfully. A case that reaches TestRail without its steps costs more than a failed export, so malformed input gets named and fixed before delivery.

FAQ

No. Attach the files, describe what you need, and answer when Casely asks which module to cover. The one place it pauses is the test plan.

That is the point. Attach an existing test case file and Casely copies the headers, their order and the writing style. No config file.

Yes. Casely writes the cases in the language of your examples.

Any tool that reads Excel: TestRail, Qase, Zephyr, Xray. The columns match whatever your team already uses.

Text-based PDFs, DOCX and XLSX work well. An image-only scan with no selectable text may not extract cleanly, so export a text version when you can.

Project structure

casely-qa-skill/
├── skill/casely/
│   ├── SKILL.md               # the skill definition and workflow
│   ├── scripts/
│   │   └── export_to_xlsx.py  # Markdown → Excel exporter
│   ├── references/            # test design, style analysis, export details
│   └── evals/                 # evaluation cases
├── examples/                  # sample spec + team style file, and a scoring rubric
├── docs/hosted-web-version.md
└── marketplace.json

Hosted version for teams

This skill runs inside your AI assistant. If your team wants a browser UI, file uploads and a review flow with no setup, join the early access list at casely.digital.

More about the hosted version →

Contributing

Read CONTRIBUTING.md before opening a pull request.

License

MIT

Made for QA engineers who find bugs. Casely writes the documents.