From lisa-rails
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.
npx claudepluginhub codyswanngt/lisa --plugin lisa-railsThis skill uses the workspace's default tool permissions.
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.
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 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: <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 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) and/or NN-name.txt/NN-name.json (text evidence)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 evidence files via gh release upload --clobber, creating CDN URLs## 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)jira issue moveNN-name-viewport.png (e.g., 01-search-step-desktop.png)NN-name.txt or NN-name.json (e.g., 01-health-check.json)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"
!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.
Ensure JIRA_API_TOKEN is set and login in ~/.config/.jira/.config.yml matches your Atlassian account email.