quality-engineering-jira-integration skillA
quality-engineering-jira-integration is agent-read markdown (skill) from hoangnguyen0403/agent-skills-standard: 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..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns 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@git:20260821.b9b1ba0mdr add hoangnguyen0403/agent-skills-standard/quality-engineering-jira-integration@sha256:c720249e4dda9d8cPin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_5hqz25yzolysoqcl)
1 badge views in 30 days
Versions
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 · 571 stars · license MIT · pushed 2026-09-24 · branch develop
API
GET https://markdownregistry.com/api/v1/artifacts/art_5hqz25yzolysoqcl 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 agent 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.
More from hoangnguyen0403/agent-skills-standard
Every file in hoangnguyen0403/agent-skills-standard