Borrowing it
Nothing to install: this file belongs to anhtester/ClaudeCode_Playwright_Demo. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/anhtester/ClaudeCode_Playwright_Demo/main/.claude/commands/generate_testcases_from_requirements.mdgit clone --depth 1 https://github.com/anhtester/ClaudeCode_Playwright_DemoWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/anhtester/claudecode_playwright_demo/generate_testcases_from_requirements)<a href="https://agentmods.dev/commands/anhtester/claudecode_playwright_demo/generate_testcases_from_requirements"><img src="https://agentmods.dev/badge/commands/anhtester/claudecode_playwright_demo/generate_testcases_from_requirements.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00020 | $0.00768 |
| Opus 5 | $0.00010 | $0.00384 |
| Sonnet 5 | $0.00004 | $0.00154 |
| Haiku 4.5 | $0.00002 | $0.00077 |
Grade A, and why
generate_testcases_from_requirements scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BẮT BUỘC (MANDATORY SKILL): Bạn PHẢI nạp và đọc kỹ nội dung của skill
rbt_manual_testing(tại.agent/skills/rbt_manual_testing/SKILL.md) trước khi bắt đầu thực hiện tác vụ này. Sử dụng Mode QUICK của skill.
Workflow: Sinh Manual Test Cases Nhanh từ Requirements
Workflow này sử dụng Mode QUICK của skill rbt_manual_testing để sinh test cases nhanh từ requirements đã sẵn có.
⚠️ Nguyên tắc
- Mode: QUICK (1 lượt duy nhất, không chờ user giữa chừng)
- Phù hợp cho module đơn giản, requirements đã rõ ràng
- Nếu phát hiện requirements quá phức tạp hoặc mơ hồ → tự động chuyển sang FULL RBT và thông báo user
- Tất cả output bằng Tiếng Việt
Các bước thực hiện
- Đọc và hiểu requirements được user cung cấp
- Xác định các luồng chính: Happy Path, Negative Path, Boundary Cases, Edge Cases
- Áp dụng kỹ thuật thiết kế test case tự động:
- Equivalence Partitioning (EP)
- Boundary Value Analysis (BVA)
- Decision Table (nếu có nhiều rules)
- State Transition (nếu có workflow)
- Validation chuyên biệt từng trường (Field-Level Validation):
- Liệt kê tất cả input fields trên form/UI
- Sinh validation TCs riêng cho TỪNG trường theo đặc tính riêng (text, email, phone, date, number, dropdown, file upload, password...)
- Áp dụng Bảng Field-Level Validation trong skill
rbt_manual_testingđể chọn validation phù hợp - KHÔNG gộp validation nhiều trường vào 1 test case
- Sinh test cases đầy đủ fields:
- TC ID (format:
[DỰ_ÁN]_[MODULE]_TC_[SỐ]) - Module
- Test Scenario / Test Case Title
- Pre-conditions
- Test Steps (đánh số)
- Expected Results (đánh số tương ứng)
- Test Data (phải cụ thể, không placeholder)
- Priority (Critical / High / Medium / Low)
- TC ID (format:
- Xuất ra bảng Markdown chuẩn
Bảng Output
| TC ID | Module | Test Scenario | Pre-Condition | Test Steps | Test Data | Expected Result | Priority |
Quy tắc quan trọng
- Test Data phải cụ thể:
[email protected], không phải "email hợp lệ" - Phải bao gồm cả Positive, Negative, Boundary, và Edge cases
- Mỗi trường input phải có validation TCs riêng (không gộp nhiều trường vào 1 TC)
- TC ID theo format thống nhất do user quy ước hoặc mặc định
[DỰ_ÁN]_[MODULE]_TC_[SỐ] - Nếu quá nhiều TCs → chia thành Part 1, Part 2 và hỏi user
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 8d ago First seen · 65 lines · 20 tokens per session scan A f23bf2b8ce56
generate_testcases_from_requirements is a command published in the GitHub repository anhtester/ClaudeCode_Playwright_Demo (2 stars, last pushed 3mo ago), licensed MIT. It adds 20 tokens to every session and 768 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
test
Write tests using MCP-powered discovery.
verify
Run repository verification using the verification-loop skill.
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
test-coverage
Analyze test coverage and identify the highest-value gaps to fill.
tdd
A command that follows test-driven development (TDD), a method where you write tests before the code they check. It moves through writing a failing test, adding the smallest implementation, and then improving the code.
check-dev
Type-check a Z specification with fuzz.