plugins/lisa-agy/skills/jira-verify/SKILL.md
This skill should be used when verifying that a JIRA ticket meets organizational standards for epic relationships and description quality. 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.
npx skillsauth add codyswanngt/lisa jira-verifyInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
All Atlassian operations in this skill go through lisa:atlassian-access. Do not call MCP tools or acli directly.
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.
lisa:atlassian-access via the Skill tool with operation: list-sites to confirm the configured site is reachable (the access skill enforces connection match against .lisa.config.json).lisa:atlassian-access operation: read-ticket key: $ARGUMENTS. Pull issue type, summary, description, parent, links, labels, components, and any custom fields needed.lisa:jira-validate-ticket and pass the ticket key. The validator fetches its own copy if needed and runs every gate (Specification + Feasibility) against the live state.Pass through lisa:jira-validate-ticket's structured output unchanged. Do not summarize or paraphrase — downstream callers (e.g. lisa:jira-agent's pre-flight gate) parse the gate lines.
parse-plan.py); the parser logic now lives inside lisa:jira-validate-ticket so this skill no longer shells out to it.development
Use Expo DOM components to run web code in a webview on native and as-is on web. Migrate web code to native incrementally.
development
Guidelines for upgrading Expo SDK versions and fixing dependency issues
development
Use when implementing or debugging ANY network request, API call, or data fetching. Covers fetch API, React Query, SWR, error handling, caching, offline support, and Expo Router data loaders (`useLoaderData`).
tools
`@expo/ui/swift-ui` package lets you use SwiftUI Views and modifiers in your app.