> quality-engineering-jira-integration
Standards for retrieving Jira issue details and linking Zephyr test cases back to Jira. Use when retrieving Jira issues or linking Zephyr test cases to Jira tickets. (triggers: **/jira_*.xml, **/test_case.json, jira issue, link zephyr, jira details, jira mcp)
curl "https://skillshub.wtf/HoangNguyen0403/agent-skills-standard/quality-engineering-jira-integration?format=md"Jira Integration Standards
Priority: P1 (HIGH)
1. Retrieving Issue Details
- Fetch Core Info: Retrieve Summary, Description, Acceptance Criteria, and Labels.
- Sibling Analysis: Identify other Jira issues with the same Component or Labels to find potentially impacted Zephyr TCs.
- Identify Links: Check for existing links to Zephyr test cases to avoid duplication.
- Actor Mapping: Extract reporter and assignee for context.
2. Linking Zephyr Test Cases
- Traceability: After creating a Zephyr Test Case, link it back to the corresponding Jira Issue.
- Format: Use the Zephyr Scale key (e.g.,
PROJ-T123) in the Jira link or comment. - Labels: Add
has-zephyr-testslabel to the Jira issue once test cases are linked.
3. Jira-Zephyr Workflow
- Fetch: Get Jira User Story details via Jira MCP.
- Generate: Create Zephyr Test Case using Zephyr Generation Skill.
- Link: Use Zephyr MCP tool
create_test_case_issue_linkto bridge the two. - Notify: Add a 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 has 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.
🚫 Anti-Patterns
- Do NOT use standard patterns if specific project rules exist.
- Do NOT ignore error handling or edge cases.
> related_skills --same-repo
> typescript-tooling
Development tools, linting, and build config for TypeScript. Use when configuring ESLint, Prettier, Jest, Vitest, tsconfig, or any TS build tooling. (triggers: tsconfig.json, .eslintrc.*, jest.config.*, package.json, eslint, prettier, jest, vitest, build, compile, lint)
> typescript-security
Secure coding practices for TypeScript. Use when validating input, handling auth tokens, sanitizing data, or managing secrets and sensitive configuration. (triggers: **/*.ts, **/*.tsx, validate, sanitize, xss, injection, auth, password, secret, token)
> typescript-language
Modern TypeScript standards for type safety and maintainability. Use when working with types, interfaces, generics, enums, unions, or tsconfig settings. (triggers: **/*.ts, **/*.tsx, tsconfig.json, type, interface, generic, enum, union, intersection, readonly, const, namespace)
> typescript-best-practices
Idiomatic TypeScript patterns for clean, maintainable code. Use when writing or refactoring TypeScript classes, functions, modules, or async logic. (triggers: **/*.ts, **/*.tsx, class, function, module, import, export, async, promise)