quality-engineering-jira-integration SKILL.md skillA
This file is byte-identical to the first copy the registry indexed, one of 3 indexed copies. Same content hash, so the same checks give both the same grade.
quality-engineering-jira-integration 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-jira-integration@git:20260714.6bf9b5ePins git:20260714.6bf9b5e 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
.codex/skills/quality-engineering/quality-engineering-jira-integration/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260714.6bf9b5e, committed Jul 14, 2026
- First version recorded
- May 20, 2026
- Size
- 2,505 bytes
- Repository stars
- 583
- License
- MIT
Trigger only when the user explicitly requests live Jira or Zephyr retrieval, existing-link inspection, linking authored test cases, label updates, or stale-link audits. Do not trigger for analysis-only prompts such as 'Analyze the acceptance criteria for TICK-4521', supplied acceptance criteria, test-case authoring, or AC-to-test generation.
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
# Jira Integration Standards ## **Priority: P1 (HIGH)** ## 1. Retrieving Issue Details - **Fetch Core Info**: Retrieve **Summary**, **Description**, **Acceptance Criteria (AC)**, and **Components**. - **Jira Key**: ALWAYS reference issue by its unique **Jira Ticket ID** (e.g., `TICK-123`). - **Sibling Analysis**: Identify other Jira issues with same **Component** or **Market Variants** (VN/MY/SG) to find potentially impacted Zephyr TCs. - **Identify Links**: Use `Get Issue Link Test Cases` with Jira issue key to check for existing linked TCs before creating duplicates. - **Actor Mapping**: Extract reporter, assignee, and **Story Points** for context. ## 2. Linking Zephyr Test Cases - **Traceability**: After creating Zephyr Test Case, link it back to corresponding Jira Issue using **Remote Link** or **Zephyr Issue Link**. - **Format**: Use Zephyr Scale key (e.g., `PROJ-T123`) in Jira link or comment. - **Labels**: Apply **`has-zephyr-tests`** label to Jira issue once test cases successfully linked. ## 3. Jira-Zephyr Workflow 1. **Fetch**: Get Jira User Story details. 2. **Generate**: Create Zephyr Test Case using generation skill. …
Read the whole file at its exact version.
How to install
mdr add hoangnguyen0403/agent-skills-standard/quality-engineering-jira-integration@sha256:c720249e4dda9d8cThe line at the top of this page pins the label git:20260714.6bf9b5e, 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_plx4zdoipggnagts)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between May 20, 2026 and Jul 14, 2026, about one every 56 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260714.6bf9b5e latest | 2026-07-14 | 6bf9b5e | 2,505 B | A | view · diff |
| git:20260520.ca51455 | 2026-05-20 | ca51455 | 2,282 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 (2505 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_plx4zdoipggnagts GET https://markdownregistry.com/api/v1/resolve?ref=hoangnguyen0403/agent-skills-standard/quality-engineering-jira-integration GET https://markdownregistry.com/api/v1/blob/c720249e4dda9d8cf7eafb722de31d4e009181558b1c2cc40ce95e6a01daa4ff
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