Quality Engineering Jira Integration Agent Skill
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.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/HoangNguyen0403/agent-skills-standard --skill quality-engineering-jira-integrationThe instruction itself
8 sections, as written by the authorJira 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 Caseswith 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-testslabel to Jira issue once test cases successfully linked.
3. Jira-Zephyr Workflow
- Fetch: Get Jira User Story details.
- Generate: Create Zephyr Test Case using generation skill.
- Link: Use SmartBear MCP tool
Create Test Case Issue Linkto bridge two. - Notify: Add comment to Jira:
Linked Zephyr Test Case: {test_case_key}.
4. Best Practices
- Concise Summaries: Keep Jira comments professional and brief.
- Traceability Matrix: Ensure every AC in Jira at least one linked Zephyr Test Case.
- Cleanup: Remove unused labels or outdated links during refactors.
5. Anti-Patterns
- No Ghosting: Create tests then link to Jira (Traceability).
- No Spam: Post single comment per link.
- No Missing Labels: Update Jira labels after linking.
Canonical response anchors
When this skill applies, preserve the following domain terminology or equivalent concrete examples in the answer when relevant:
- Identify
- has-zephyr-tests label
Other skills for the same job
different authors, same section of the catalogue
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Intelligently organizes your files and folders across your computer by understanding context, finding duplicates, suggesting better structures, and automating cleanup tasks. Reduces cognitive load and keeps your digital workspace tidy without manual effort.
Generates creative domain name ideas for your project and checks availability across multiple TLDs (.com, .io, .dev, .ai, etc.). Saves hours of brainstorming and manual checking.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.
Creative research ideation and exploration. Use for open-ended brainstorming sessions, exploring interdisciplinary connections, challenging assumptions, or identifying research gaps. Best for early-stage research planning when you do not have specific observations yet. For formulating testable hypotheses from data use hypothesis-generation.
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
How to use it
Take hoangnguyen0403/quality-engineering-jira-integration from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.