skills.rest
CodySwannGT
CodySwannGTCOMMUNITY
Explore all skills by this author →
GitHub

jira-verify

Validate JIRA tickets for epic links, description completeness, and frontend Validation Journey sections.

3|3|Updated Jan 18, 2026
Search Tags:#jira#ticket verification#epic relationship#description quality#frontend validation#workflow standards
One-click install
npx skills add https://github.com/CodySwannGT/lisa --skill jira-verify
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: jira-verify
Source: https://github.com/CodySwannGT/lisa/tree/main/plugins/lisa-expo/skills/jira-verify
Command: npx skills add https://github.com/CodySwannGT/lisa --skill jira-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires mcp__atlassian, and includes scripts (resource) components.

What problem does it solve?

This skill ensures that JIRA tickets meet essential organizational standards for epic relationships and description quality, preventing issues downstream in the development process.

Core Features & Use Cases

  • Epic Relationship Validation: Checks if non-bug/non-epic tickets are correctly linked to an epic parent.
  • Description Quality Assurance: Validates that ticket descriptions contain necessary details for different audiences (coding assistants, developers, stakeholders).
  • Frontend Ticket Validation: Ensures tickets impacting the UI include a "Validation Journey" section.
  • Use Case: Before a developer starts working on a new feature ticket, this skill can be run to confirm it's properly set up, has clear requirements, and is linked to the correct epic, saving time and preventing rework.

Quick Start

Run the jira-verify skill to check the JIRA ticket with ID 'PROJ-123'.

Frequently Asked Questions about jira-verify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate JIRA ticket standards for epic relationships and description quality?▼

To validate JIRA ticket standards, run a verification process that checks non-bug/non-epic tickets for required epic parent links and ensures descriptions contain necessary details for coding assistants, developers, and stakeholders.

How do I ensure frontend JIRA tickets include a Validation Journey section?▼

To ensure frontend JIRA tickets include a Validation Journey section, use ticket validation scripts to parse and verify that UI-impacting tickets contain this specific section before development begins.

Do I need the Atlassian integration to check JIRA tickets for missing epic links?▼

Yes, you need the Atlassian integration active to check JIRA tickets for missing epic links, as the verification process depends on the Atlassian API connection to access and validate ticket data.

What is the best way to verify JIRA descriptions are complete for developers and stakeholders?▼

The best way to verify JIRA descriptions are complete is to use an automated validation tool that checks if ticket descriptions cater to coding assistants, developers, and stakeholders before work begins.

What are the limitations of automated JIRA ticket verification?▼

Automated JIRA ticket verification is limited to checking structural standards like epic parent links, description completeness, and frontend Validation Journey sections, and cannot assess the qualitative accuracy of the content.

Related Skills

Explore More Product & Management Skills→
thisisqubikathisisqubika

fetch-ticket-context

Gather Jira ticket details, comments, links, and attachments into a markdown file.

Official
Advanced
OreStudioOreStudio
25

new-sprint-skill

Update sprint backlog files, version strings, and CI configuration for a new Agile sprint.

Official
Intermediate
BerryKuipersBerryKuipers
7

create-pull-request

Create GitHub pull requests with linked issues and template-based bodies.

Community
Intermediate
Yona544Yona544
1

ms365-tenant-manager

Automates Microsoft 365 tenant setup, administration, and governance workflows.

Community
Advanced