codyswanngt/jira-evidence
plugins/lisa-rails-agy/skills/jira-evidence/SKILL.md
Upload evidence to GitHub pr-assets release, update PR description, upload attachments to JIRA, post comment, and move ticket to Code Review. Reusable by any skill that captures evidence and generates evidence/comment.txt + evidence/comment.md.
$ install --global
skillsauthnpx skillsauth add codyswanngt/lisa jira-evidenceInstall 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: Apr 20, 2026, 3:27 AM19.2s2 files scanned
SKILL.md
- name:
- jira-evidence
- description:
- Upload evidence to GitHub pr-assets release, update PR description, upload attachments to JIRA, post comment, and move ticket to Code Review. Reusable by any skill that captures evidence and generates evidence/comment.txt + evidence/comment.md.
JIRA Evidence Posting
Upload captured evidence and generated templates to GitHub PR description and JIRA ticket. This skill is the posting step — it assumes evidence files and comment templates already exist in the evidence directory.
Arguments
$ARGUMENTS: <TICKET_ID> <EVIDENCE_DIR> <PR_NUMBER>
TICKET_ID(required): JIRA ticket key (e.g.,PROJ-123)EVIDENCE_DIR(required): Directory containing evidence and templates (e.g.,./evidence)PR_NUMBER(required): GitHub PR number to update description
Prerequisites
JIRA_API_TOKENenvironment variable setjira-cliconfigured (~/.config/.jira/.config.yml) — server and login are read from thereghCLI authenticated- Evidence directory containing:
- Evidence files:
NN-name-viewport.png(screenshots) and/orNN-name.txt/NN-name.json(text evidence) comment.txt— JIRA wiki markup (generated bygenerate-templates.py)comment.md— GitHub markdown (generated bygenerate-templates.py)
- Evidence files:
Usage
bash .claude/skills/jira-evidence/scripts/post-evidence.sh <TICKET_ID> <EVIDENCE_DIR> <PR_NUMBER>
Example
bash .claude/skills/jira-evidence/scripts/post-evidence.sh PROJ-123 ./evidence 42
What It Does
- Read JIRA config — Reads
~/.config/.jira/.config.ymlto obtainserverandlogindynamically (no hardcoded values) - Upload to GitHub
pr-assetsrelease — Uploads evidence files viagh release upload --clobber, creating CDN URLs - Update PR description — Replaces or appends the
## Evidencesection in the PR body usinggh pr edit - Upload JIRA attachments — Uploads image evidence via REST API v3 so
!filename.png!wiki markup renders inline - Post JIRA comment — Posts
comment.txtas a new comment via REST API v2 (wiki markup) - Move ticket to Code Review — Transitions the JIRA ticket via
jira issue move
Evidence Naming Conventions
- Image evidence:
NN-name-viewport.png(e.g.,01-search-step-desktop.png) - Text evidence:
NN-name.txtorNN-name.json(e.g.,01-health-check.json)
Troubleshooting
Images not rendering in GitHub PR
Images must be in the pr-assets GitHub release. If the release does not exist, create it first:
gh release create pr-assets --title "PR Assets" --notes "CDN for PR evidence"
JIRA comment shows !filename.png! as text (not image)
The screenshot must be uploaded as a JIRA attachment before posting the comment. The script uploads attachments first then posts the comment.
JIRA API returns 403 on attachment upload
Ensure JIRA_API_TOKEN is set and login in ~/.config/.jira/.config.yml matches your Atlassian account email.
Related Skills
codyswanngt/use-dom
development
VerifiedTrustedCommunity
Use Expo DOM components to run web code in a webview on native and as-is on web. Migrate web code to native incrementally.
1SKILL.mdUpdated Jun 6, 2026
codyswanngt/upgrading-expo
development
VerifiedTrustedCommunity
Guidelines for upgrading Expo SDK versions and fixing dependency issues
1SKILL.mdUpdated Jun 6, 2026
codyswanngt/native-data-fetching
development
VerifiedTrustedCommunity
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`).
1SKILL.mdUpdated Jun 6, 2026
codyswanngt/Expo UI SwiftUI
tools
VerifiedTrustedCommunity
`@expo/ui/swift-ui` package lets you use SwiftUI Views and modifiers in your app.
1SKILL.mdUpdated Jun 6, 2026