From lisa-expo
Upload screenshots to GitHub pr-assets release, update PR description with evidence, upload attachments to JIRA, post wiki markup comment, and move ticket to Code Review. Reusable by any skill that captures screenshots and generates evidence/comment.txt + evidence/comment.md.
npx claudepluginhub codyswanngt/lisa --plugin lisa-expoThis skill uses the workspace's default tool permissions.
Upload captured screenshots and generated templates to GitHub PR description and JIRA ticket. This skill is the posting step — it assumes screenshots and comment templates already exist in the evidence directory.
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
Upload captured screenshots and generated templates to GitHub PR description and JIRA ticket. This skill is the posting step — it assumes screenshots and comment templates already exist in the evidence directory.
$ARGUMENTS: <TICKET_ID> <EVIDENCE_DIR> <PR_NUMBER>
TICKET_ID (required): JIRA ticket key (e.g., PROJ-123)EVIDENCE_DIR (required): Directory containing screenshots and templates (e.g., ./evidence)PR_NUMBER (required): GitHub PR number to update descriptionJIRA_API_TOKEN environment variable setjira-cli configured (~/.config/.jira/.config.yml) — server and login are read from theregh CLI authenticatedNN-name-viewport.png screenshots (numbered, e.g., 01-search-step-desktop.png)comment.txt — JIRA wiki markup (generated by generate-templates.py)comment.md — GitHub markdown (generated by generate-templates.py)bash .claude/skills/jira-evidence/scripts/post-evidence.sh <TICKET_ID> <EVIDENCE_DIR> <PR_NUMBER>
bash .claude/skills/jira-evidence/scripts/post-evidence.sh PROJ-123 ./evidence 42
~/.config/.jira/.config.yml to obtain server and login dynamically (no hardcoded values)pr-assets release — Uploads NN-name-viewport.png screenshots via gh release upload --clobber, creating CDN URLs that render in GitHub markdown## Evidence section in the PR body using gh pr edit!filename.png! wiki markup renders inlinecomment.txt as a new comment via REST API v2 (wiki markup with embedded images)jira issue moveOnly files matching NN-*.png (two-digit prefix) are uploaded. Other files in the evidence directory are ignored.
evidence/
01-search-step-desktop.png ✓ uploaded
02-confirm-step-desktop.png ✓ uploaded
03-search-step-mobile.png ✓ uploaded
comment.txt used for JIRA comment
comment.md used for PR description
Images must be in the pr-assets GitHub release (not committed to git). The script handles this via gh release upload. If the release does not exist, create it first:
gh release create pr-assets --title "PR Assets" --notes "CDN for PR evidence screenshots"
!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 — always in that order.
Ensure JIRA_API_TOKEN is set and login in ~/.config/.jira/.config.yml matches your Atlassian account email.