quality-engineering-zephyr-test-generation SKILL.md skillA
quality-engineering-zephyr-test-generation from hoangnguyen0403/agent-skills-standard is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add hoangnguyen0403/agent-skills-standard/quality-engineering-zephyr-test-generation@git:20260913.bef7b5cPins git:20260913.bef7b5c in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- hoangnguyen0403/agent-skills-standard
- Path
.agents/skills/quality-engineering/quality-engineering-zephyr-test-generation/SKILL.md- Versions recorded
- 4
- Latest version
- git:20260913.bef7b5c, committed Sep 13, 2026
- First version recorded
- May 20, 2026
- Size
- 5,139 bytes
- Repository stars
- 583
- License
- MIT
Generate Zephyr test cases from Jira stories: parse acceptance criteria and business rules, impact-analyze existing TCs (update vs. create new), and draft correctly named test cases. Use for AC-to-test generation; defer post-generation Jira linking and manual test-case quality review.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Zephyr Test Generation Standards
## **Priority: P1 (HIGH)**
## Workflow: Jira → Zephyr
1. **Analyze Requirements**:
- Extract: Summary, ACs, Platform per AC row, Market, Components.
- Fetch Jira with `?expand=renderedFields` — HTML authoritative for platform colors:
`#00B8D9` = Web · `#36B37E` = Mobile · `#FF991F` = Web+Mobile
- See [Actor/Permission Matrix](../quality-engineering-business-analysis/references/analysis_patterns.md) for role/market logic.
- HALT on ambiguous AC per `quality-engineering-test-plan-authoring` scenario expansion: ultra-short AC, no expected behavior, bundled ACs, contradiction. Ask before drafting.
2. **Impact Analysis** (run before any TC creation)
- **Step — Direct Lookup**: Call `Get Issue Link Test Cases` with Jira issue key (e.g., `{PROJECT}-{ID}`).
- **Step B — Supplemental**: If Step 0, search by `[Module]` and `[Screen]` keywords + check sibling issue links.
- See [Discovery Protocol](references/impact_analysis.md) for full chain.
- Map each AC to coverage status:
- **Covered** → ask user: skip or update to current format?
- **Partial** → always propose NEW TC.
- **Not Covered** → always create NEW TC.
3. **Draft Artifact**:
…Read the whole file at its exact version.
How to install
mdr add hoangnguyen0403/agent-skills-standard/quality-engineering-zephyr-test-generation@sha256:d093ffbbc04ddda7The line at the top of this page pins the label git:20260913.bef7b5c, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_6zdaxmfgjkd6rfcf)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between May 20, 2026 and Sep 13, 2026, about one every 39 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260913.bef7b5c latest | 2026-09-13 | bef7b5c | 5,139 B | A | view · diff |
| git:20260714.6bf9b5e | 2026-07-14 | 6bf9b5e | 5,243 B | A | view · diff |
| git:20260627.0588377 | 2026-06-27 | 0588377 | 4,911 B | A | view · diff |
| git:20260520.ca51455 | 2026-05-20 | ca51455 | 4,902 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (5139 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
hoangnguyen0403/agent-skills-standard · 583 stars · license MIT · pushed 2026-11-07 · branch develop
API
GET https://markdownregistry.com/api/v1/artifacts/art_6zdaxmfgjkd6rfcf GET https://markdownregistry.com/api/v1/resolve?ref=hoangnguyen0403/agent-skills-standard/quality-engineering-zephyr-test-generation GET https://markdownregistry.com/api/v1/blob/d093ffbbc04ddda781592ea286b582450e42adb94b7c547548f36235f6f40fb1
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from hoangnguyen0403/agent-skills-standard
Every file in hoangnguyen0403/agent-skills-standard