hoangnguyen0403/quality-engineering-jira-integration
skills/quality-engineering/quality-engineering-jira-integration/SKILL.md
Jira ↔ Zephyr traceability: fetch story AC and components, detect existing TC links, link new Zephyr TCs back to Jira, and apply has-zephyr-tests labels. Use after creating Zephyr test cases that need linking, when fetching a Jira story's details for test generation, or when auditing and cleaning up stale TC links.
$ install --global
skillsauthnpx skillsauth add hoangnguyen0403/agent-skills-standard quality-engineering-jira-integrationInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 20, 2026, 3:06 AM103.1s2 files scanned
SKILL.md
- name:
- quality-engineering-jira-integration
- description:
- Jira ↔ Zephyr traceability: fetch story AC and components, detect existing TC links, link new Zephyr TCs back to Jira, and apply has-zephyr-tests labels. Use after creating Zephyr test cases that need linking, when fetching a Jira story's details for test generation, or when auditing and cleaning up stale TC links.
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 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.
Related Skills
hoangnguyen0403/common-software-requirements
development
VerifiedTrustedCommunity
Standardize SRS and FRS specifications for technical behavior, interfaces, data contracts, quality constraints, and verification mapping. Use when writing SRS, functional specification, system behavior requirements, API/data contracts, or non-functional thresholds.
503SKILL.mdUpdated May 23, 2026
hoangnguyen0403/common-business-requirements
development
VerifiedTrustedCommunity
Standardize BRD and BRD-lite discovery for business goals, stakeholder impact, current-to-future state, and measurable value outcomes. Use when creating BRD, business case, project justification, ROI narrative, or AS-IS to TO-BE scope.
503SKILL.mdUpdated May 23, 2026
hoangnguyen0403/common-tdd
development
VerifiedTrustedCommunity
Implements a strict Red-Green-Refactor loop to ensure zero production code is written without a prior failing test. Use when: creating new features, fixing bugs, or expanding test coverage.
503SKILL.mdUpdated May 10, 2026
hoangnguyen0403/common-product-requirements
testing
VerifiedTrustedCommunity
Standardize PRD discovery and drafting for product scope, user outcomes, requirement IDs, and acceptance criteria. Use when creating PRD, product requirements, feature specification, or acceptance criteria plan.
503SKILL.mdUpdated May 10, 2026