How do I install the Jira Verify skill?

Run npx skillmds@latest add majiayu000/jira-verify-3 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Jira Verify safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Jira Verify?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Jira Verify free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Jira Verify?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Jira Verify by majiayu000 — Agent Skill

Name: Jira Verify
Rating: 4.666666666666667 (3 reviews)
Author: majiayu000

Jira Verify

This skill should be used when verifying that a JIRA ticket meets organizational standards for epic relationships and description quality. It checks epic parent relationships and validates description completeness for coding assistants, developers, and stakeholders.

majiayu000 Updated Sep 22, 2026 567 repo stars

File contents

Verify JIRA Ticket: $ARGUMENTS

Fetch ticket $ARGUMENTS and verify it meets organizational standards.

Verification Checks

1. Epic Parent Relationship

Rule: Non-bug, non-epic tickets MUST have an epic parent

If missing: Search filter 10089 (Epic Backlog) and suggest appropriate epics

2. Description Quality

Verify description adequately addresses:

Coding Assistants: Acceptance criteria, requirements, constraints, I/O Developers: Technical context, integration points, testing, edge cases Stakeholders: Business value, user impact, success metrics, summary

3. Validation Journey (Frontend Tickets)

Rule: Tickets that touch UI (components, labels, or description mentioning frontend, UI, modal, layout, responsive, screen, page, button, form) MUST include a Validation Journey section.

Check by running:

python3 .claude/skills/jira-journey/scripts/parse-plan.py <TICKET_ID> 2>&1

If the parser returns steps: PASS
If the parser fails with "No 'Validation Journey' section found": FAIL — recommend using /jira-add-journey <TICKET_ID> to add one

This check is skipped for:

Pure backend/API tickets (no UI surface)
Config-only tickets (env vars, feature flags, CI/CD)
Epic-level tickets (journeys belong on child stories/tasks)

Execute Verification

Retrieve ticket details, run all checks, and provide specific improvement recommendations for any failures.

Frequently asked questions