Loading...
Loading...
Found 75 Skills
Generates high-quality Gherkin (BDD) scenarios from functional requirements using a two-agent iterative cycle: a generator agent that creates/modifies the Gherkin and a reviewer agent that validates it and proposes improvements. The cycle repeats automatically until the Gherkin passes review. Use this skill whenever the user mentions: "generate Gherkin", "BDD scenarios", "Gherkin test cases", "Feature/Scenario/Given/When/Then", "requirements to Gherkin", "BDD specifications", or asks to transform functional requirements into behaviour tests. Also applies when the user brings a requirements document and wants test cases, acceptance criteria, or user stories with executable examples.
Systematic LLM prompt engineering: analyzes existing prompts for failure modes, generates structured variants (direct, few-shot, chain-of-thought), designs evaluation rubrics with weighted criteria, and produces test case suites for comparing prompt performance. Triggers on: "prompt engineering", "prompt lab", "generate prompt variants", "A/B test prompts", "evaluate prompt", "optimize prompt", "write a better prompt", "prompt design", "prompt iteration", "few-shot examples", "chain-of-thought prompt", "prompt failure modes", "improve this prompt". Use this skill when designing, improving, or evaluating LLM prompts specifically. NOT for evaluating Claude Code skills or SKILL.md files — use skill-evaluator instead.
Find branch coverage gaps in changed code and fix them by writing missing tests. Two analysis layers: Source ↔ Test (logic branches vs test cases) and Spec ↔ Test (requirement scenarios vs test cases, when a spec file is provided). Use when verifying test completeness after implementing a feature or fixing a bug, when auditing whether tests match a spec, or when suspecting untested branches.
Analyze, prioritize, and document test cases in TMS (Jira/Xray) -- the bridge between manual QA and test automation. Use when creating Test/ATP/ATR artifacts, calculating ROI to choose which tests to automate, maintaining US-ATP-ATR-TC traceability, or repairing broken TMS links. Supports four scopes: module-driven (exhaustive module exploration), ticket-driven (QA-approved user story), bug-driven (regression TC for a closed bug), and ad-hoc/exploratory. Produces three outcomes per TC: Candidate (feeds test-automation), Manual (terminal), Deferred (terminal). Triggers on: document tests, create test cases in Jira/Xray, prioritize for automation, ROI analysis, which tests to automate, Candidate vs Manual, link ATP to ATR, fix TMS traceability, stage 4, turn this bug into a regression test. Do NOT use for writing test code (test-automation) or running suites (regression-testing).
Use when you need to generate or update `{FEATURE_DIR}/verification/usecase.md` (test cases) during the verification phase of the Spec Pack, and require AC traceability and a structure that supports automated script generation.
Universal generation template for OpenHarmony XTS test cases. Supports test case generation for various subsystems, API definition parsing, test coverage analysis, and code specification checking. Trigger keywords: XTS, test generation, case generation, test case.
Debug regex patterns with visual breakdowns, plain English explanations, test case generation, and flavor conversion. Use when user needs help with regular expressions or pattern matching.
Convert feature requirements into structured end-to-end test cases as JSON.
Creates a QA planning subtask in the configured issue tracker tagged `qa-plan`, with test cases derived only from the ticket's functional and technical requirements.
Design accessibility testing plans and test cases covering WCAG 2.1 standards, screen readers, and keyboard navigation. Default output is Markdown, with support for requesting Excel/CSV/JSON formats. Use for accessibility testing.
Smoke test for alicloud-ai-cloud-call-center. Validate minimal authentication, API reachability, and one read-only query path.
Analyze test coverage gaps and generate tests to improve coverage. Use when improving test coverage, finding untested code, or writing missing tests.