SkillAgentSearch skills...

create-test-cases

Author human-readable manual test cases (markdown) into the project's docs/living-test-cases/ — the living artifact that /qa:manual-test-run executes

Install / Use

npx skills add syahiidkamil/Software-Engineer-AI-Agent-Atlas

Installs into whichever agent you are using.

About this skill
⚡

Claude Commands

Claude Code slash commands

Quality Score

85/100

Supported Platforms

Claude Code

Tags

Our assessment of create-test-cases

create-test-cases scores 85/100 on our quality scale, 763rd of 1,155 Content & Media skills we index.

Its Claude Commands is 3.4 KB long, well organised into 10 sections with 3 code examples: a solid amount of guidance for an agent.

It has 406 GitHub stars, a meaningful sign that others use it.

Substance
26/30
Structure
18/20
Description
15/15
Adoption
11/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 15 days ago, so create-test-cases is actively maintained.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-11-12. Automated pattern scan on 2026-11-12. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

create-test-cases compared with similar skills

All 4 of these similar skills score higher than create-test-cases; compare them before choosing.

SkillScoreStarsUpdatedFormat
create-test-cases (this skill)by syahiidkamil8540615d agoClaude Commands
claude-memby thedotmack100117.6ktodayCLAUDE.md
taste-skillby Leonxlnx100116.8k8d agoCLAUDE.md
Agent-Reachby Panniantong100112.3k8d agoCLAUDE.md
Understand-Anythingby Egonex-AI10092.8k1d agoCLAUDE.md

Frequently asked questions

How do I install create-test-cases?
Run npx skills add syahiidkamil/Software-Engineer-AI-Agent-Atlas. The install tabs above show the steps for each supported agent.
Which AI agents does create-test-cases work with?
It is written for Claude Code, as a Claude Commands file. Other agents that read the same format can often use it too.
Is create-test-cases safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is create-test-cases still maintained?
The repository was last updated 15 days ago, so create-test-cases is actively maintained.

description: Author human-readable manual test cases (markdown) into the project's docs/living-test-cases/ — the living artifact that /qa:manual-test-run executes argument-hint: "[project] feature-or-area"

You are ATLAS in QA mode. Boss wants manual test cases written for a feature or area. These are living test cases: human-readable markdown that lives in <P>/docs/living-test-cases/, is maintained as the product evolves, and is executed in a real browser by the manual-qa-haiku runner (or manual-qa-sonnet for exploratory and visual checks) via /qa:manual-test-run.

Resolve the project root <P> first (the argument, the project this session is on, or ask once). You write the cases here, in the main session, on the strongest model; the cheaper runner only executes them. That split works only if every step is explicit and every expected result is observable.

The feature/area is provided as argument: $ARGUMENTS

If none is provided, use AskUserQuestion: "What feature or area should I write test cases for?"

Never generate .spec.ts, playwright.config.ts, Jest/vitest/mocha/Cypress specs, or any other test-runner code. No test framework is installed and none should be added. Author markdown only — the cases are executed manually by an agent driving a real browser, not by a runner.

Step 1: Understand what to test

Read what's relevant before drafting — the feature's phase.html if it came from /plan:create-phase (its acceptance checks are the seed), the live UI/route, the code paths, or whatever Boss points you at. Then, with Theory of Mind, model the end user: what they'll actually do, what they fear, where they'll fat-finger input. If scope is unclear, ask in one focused batch (the primary flows, the must-cover edge cases, the priority bar).

Step 2: Draft the cases

Write to <P>/docs/living-test-cases/{feature-slug}/:

<P>/docs/living-test-cases/{feature-slug}/
├── README.md          # index: what this covers, one line per case with priority
├── TC-001.md
├── TC-002.md
└── ...

Each TC-{NNN}.md:

# TC-{NNN}: {Title}

## Type
{smoke | happy-path | edge-case | error-handling | regression}

## Priority
{critical | high | medium | low}

## Preconditions
{state that must exist before this test}

## Steps
1. {action}
2. {action}

## Expected Result
{observable, verifiable outcome: visible text, URL, element state}

Write each step as one action a tester can take without guessing ("Click Pay now", not "complete checkout"), and each expected result as something visible. A runner marks a case UNSURE when it can't observe the outcome, so vague cases waste runs.

Cover the spread that matters — does the basic flow work (smoke), does the main use case work (happy path), what breaks on bad input or odd state (edge), does it fail gracefully (error handling). Don't pad the count; each case should earn its place.

Step 3: Review with Boss

Show the index and use AskUserQuestion: "I've drafted {N} cases for {feature}. Review, add, or adjust priorities?" Iterate until it lands.

Step 4: Summary

Report the folder, the case count by priority, and the next step:

Test cases created: <P>/docs/living-test-cases/{feature-slug}/ — {N} cases ({critical}/{high}/{med}/{low})

Next: run them with /qa:manual-test-run <project> {feature-slug}
      (results land in <P>/misc/test-runs/)

Remind Boss: "Run git diff to review. When ready, I'll commit."

Related Skills

View on GitHub
GitHub Stars406
CategoryContent
Updated15d ago
Forks60

Languages

JavaScript

Trust signals

88/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium