codyswanngt/lisa-jira-verify
plugins/lisa/skills/lisa-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.
$ install --global
skillsauthnpx skillsauth add codyswanngt/lisa lisa-jira-verifyInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jul 8, 2026, 4:09 AM193.5s2 files scanned
SKILL.md
- name:
- lisa-jira-verify
- description:
- 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.
- allowed-tools:
- ["Skill"]
Verify JIRA Ticket: $ARGUMENTS
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.
Process
- Invoke
lisa-atlassian-accessvia the Skill tool withoperation: list-sitesto confirm the configured site is reachable (the access skill enforces connection match against.lisa.config.json). - Fetch the ticket via
lisa-atlassian-accessoperation: read-ticket key: $ARGUMENTS. Pull issue type, summary, description, parent, links, labels, components, and any custom fields needed. - Invoke
lisa-jira-validate-ticketand pass the ticket key. The validator fetches its own copy if needed and runs every gate (Specification + Feasibility) against the live state. - Surface the validator's report verbatim to the caller.
Output
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.
Notes
- This skill is read-only. It never edits the ticket, posts comments, or changes status.
- If a gate fails, the recommendation is part of the validator's report; surface it as-is.
- Validation Journey checks (S11) historically required a parser script (
parse-plan.py); the parser logic now lives insidelisa-jira-validate-ticketso this skill no longer shells out to it.
Related Skills
codyswanngt/lisa-setup-sonar
tools
VerifiedTrustedCommunity
Configure the official SonarQube plugin + MCP as Lisa's single Sonar substrate across every supported coding agent. Installs/updates the SonarQube CLI, authenticates (browser login on a dev machine, or SONARQUBE_CLI_TOKEN headless), selects the Test Manager target, runs `sonar integrate <agent>` for each supported agent (Claude, Codex, Cursor, Copilot, Antigravity) and wires the MCP for OpenCode, then writes only non-secret policy to .lisa.config.json. Separate from the CI SonarCloud scan gate, which is unchanged.
1SKILL.mdUpdated Jul 24, 2026
codyswanngt/lisa-setup-sonar
tools
VerifiedTrustedCommunity
Configure the official SonarQube plugin + MCP as Lisa's single Sonar substrate across every supported coding agent. Installs/updates the SonarQube CLI, authenticates (browser login on a dev machine, or SONARQUBE_CLI_TOKEN headless), selects the Test Manager target, runs `sonar integrate <agent>` for each supported agent (Claude, Codex, Cursor, Copilot, Antigravity) and wires the MCP for OpenCode, then writes only non-secret policy to .lisa.config.json. Separate from the CI SonarCloud scan gate, which is unchanged.
1SKILL.mdUpdated Jul 24, 2026
codyswanngt/lisa-setup-sonar
tools
VerifiedTrustedCommunity
Configure the official SonarQube plugin + MCP as Lisa's single Sonar substrate across every supported coding agent. Installs/updates the SonarQube CLI, authenticates (browser login on a dev machine, or SONARQUBE_CLI_TOKEN headless), selects the Test Manager target, runs `sonar integrate <agent>` for each supported agent (Claude, Codex, Cursor, Copilot, Antigravity) and wires the MCP for OpenCode, then writes only non-secret policy to .lisa.config.json. Separate from the CI SonarCloud scan gate, which is unchanged.
1SKILL.mdUpdated Jul 24, 2026
codyswanngt/lisa-setup-sonar
tools
VerifiedTrustedCommunity
Configure the official SonarQube plugin + MCP as Lisa's single Sonar substrate across every supported coding agent. Installs/updates the SonarQube CLI, authenticates (browser login on a dev machine, or SONARQUBE_CLI_TOKEN headless), selects the Test Manager target, runs `sonar integrate <agent>` for each supported agent (Claude, Codex, Cursor, Copilot, Antigravity) and wires the MCP for OpenCode, then writes only non-secret policy to .lisa.config.json. Separate from the CI SonarCloud scan gate, which is unchanged.
1SKILL.mdUpdated Jul 24, 2026