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 the configured review status only when `jira.workflow.review` is set (otherwise leave it in `claimed`). 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: Aug 27, 2026, 4:05 AM260.8s2 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 the configured review status only when `jira.workflow.review` is set (otherwise leave it in `claimed`). 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 set- a jira-cli config —
.lisa/jira-cli/.config.ymlif thesetup-jira-cliSessionStart hook wrote one, otherwise~/.config/.jira/.config.yml.serverandloginare read from whichever is used, and the fallback is announced on stderr rather than taken silently. ghCLI 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 — Resolves the jira-cli config (
$PROJECT_DIR/.lisa/jira-cli/.config.ymlfirst, then~/.config/.jira/.config.yml, announcing the fallback) and readsserverandloginfrom it dynamically — no hardcoded values. Exits 1 naming both paths when neither exists. The same resolved path is then passed tojira issue moveas--config, so the CLI cannot end up on a different config than the one this script parsed. - 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 the configured review status — Resolves
jira.workflow.review(or thejira.workflow.code_reviewalias) from.lisa.config.json/.lisa.config.local.jsonand transitions viajira issue move.reviewis optional; when unset, the ticket stays inclaimedand this step is skipped. Never transition to a status not named inconfig.jira.workflow. If the configured status is not a valid transition from the current state, log a warning and skip.
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 the resolved jira-cli config (.lisa/jira-cli/.config.yml, else ~/.config/.jira/.config.yml) matches your Atlassian account email.
Related Skills
codyswanngt/lisa-setup-workstation
development
VerifiedTrustedCommunity
Prepare a machine — a fresh laptop or a throwaway container — to run coding agents, before any repository exists. Detects which of Lisa's supported agents (Claude Code, Codex, Cursor, OpenCode, Antigravity, Copilot) are already installed, asks which credential manager the machine uses (Bitwarden, 1Password, Doppler, Vault, AWS, or none), and installs only what is missing, each by its vendor's own preferred method. Idempotent, headless by default, and emits a Dockerfile for a spin-up/spin-down environment. Run it on a new machine, in a container, or before cloning anything.
3SKILL.mdUpdated Aug 30, 2026
codyswanngt/lisa-setup-remote-env
tools
VerifiedTrustedCommunity
Provision and verify a remote execution environment for a host project — Codex Cloud today, other remote surfaces as they are added. Generates a repository-owned setup script that installs the declared toolchain, materializes secrets through lisa-secrets-access, and runs the project's own hook. Provisions by API where one exists, by driving the vendor console where one does not, and by emitting exact config otherwise — then proves the result with the same read-back regardless of which tier did the work. Use before dispatching any work with executionEnv.
3SKILL.mdUpdated Aug 30, 2026
codyswanngt/lisa-setup-local-env
tools
VerifiedTrustedCommunity
Bring a developer's machine in line with the toolchain the project declares. Reports every tool in remoteEnv.tools that is missing, outdated, or unpinned for this platform, and installs the missing ones into ~/.local/bin from the same pinned, checksummed entries the remote surfaces use — but only when asked. Same manifest, same pins, same installers as lisa-setup-remote-env; what differs is consent and that the pin is a floor rather than an equality. Run it on a fresh checkout, after a manifest change, or when a tool fails at the moment of use.
3SKILL.mdUpdated Aug 30, 2026
codyswanngt/lisa-remote-dispatch
tools
VerifiedTrustedCommunity
Route one unit of work to a remote execution surface. Reads the executionEnv parameter (local by default, codex-cloud or claude-web today), verifies the environment is provisioned and bound to this repository, submits a thin skill invocation, records the task identifier to .lisa/remote-dispatch.json, and exits without polling. Routing only — the remote runs the identical skill from the identical repository. Composable and inline: other skills invoke it via the Skill tool rather than users calling it directly.
3SKILL.mdUpdated Aug 30, 2026