How do I install the Jira Verify skill?

Run npx skillmds@latest add codyswanngt/jira-verify 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. 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?

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

Jira Verify by codyswanngt — Agent Skill

Name: Jira Verify
Author: codyswanngt

Jira Verify

This skill should be used when verifying that a JIRA ticket meets organizational standards for epic relationships, description quality, and (for UI tickets) Validation Journey presence. It fetches the live ticket and delegates the gate checks to jira-validate-ticket so the bar matches what jira-write-ticket enforces pre-write.

codyswanngt 0d5c736 2 files · 2.2 KB Updated Sep 17, 2026

File contents

Verify JIRA Ticket: $ARGUMENTS

Verify that the existing JIRA ticket $ARGUMENTS meets organizational standards. This skill is a thin post-write wrapper around lisa:jira-validate-ticket: it fetches the live ticket and asks lisa:jira-validate-ticket to run the gates against the fetched state.

This indirection exists so the gate definitions live in exactly one place (lisa:jira-validate-ticket). When the bar changes, change it there — lisa:jira-verify, lisa:jira-write-ticket (Phase 5.5 pre-write), and lisa:notion-to-tracker (PRD dry-run) all pick it up.

Process

Resolve cloud ID via mcp__atlassian__getAccessibleAtlassianResources.
Fetch the ticket via mcp__atlassian__getJiraIssue for $ARGUMENTS.
Invoke lisa:jira-validate-ticket and pass the ticket key. The validator runs every gate (Specification + Feasibility) against the live state, including the Validation Journey check (S11) which applies to any runtime-behavior change — UI tickets in Expo always qualify.
Surface the validator's report verbatim.

Output

Pass through lisa:jira-validate-ticket's structured output unchanged. Downstream callers parse the gate lines.

Notes

This skill is read-only. It never edits the ticket, posts comments, or changes status.
For UI tickets that fail the Validation Journey gate, the validator's remediation will recommend /lisa:jira-add-journey — the Expo flavor of lisa:jira-add-journey produces the [SCREENSHOT: ...] + viewport block that the Playwright-based journey runner consumes.

Frequently asked questions