codyswanngt/jira-evidence
plugins/lisa/skills/jira-evidence/SKILL.md
Upload text evidence to GitHub pr-assets release, update PR description, post JIRA comment with code blocks, and move ticket to the configured code-review status. 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: May 27, 2026, 4:14 AM236.0s3 files scanned
SKILL.md
- name:
- jira-evidence
- description:
- Upload text evidence to GitHub pr-assets release, update PR description, post JIRA comment with code blocks, and move ticket to the configured code-review status. Reusable by any skill that captures evidence and generates evidence/comment.txt + evidence/comment.md.
JIRA Evidence Posting
Workflow resolution
The post-build review status is read from .lisa.config.json jira.workflow.review (or jira.workflow.code_review), falling back to Code Review. JIRA does not have a separate review role in the canonical config schema (the build lifecycle stays in claimed until done); this skill uses the project's actual post-build review status when one exists. If the configured status is not a valid transition from the ticket's current state, log a warning and skip the transition — the human will handle it.
REVIEW="Code Review"
if [ -f .lisa.config.json ]; then
_cfg=$(jq -r '.jira.workflow.review // .jira.workflow.code_review // empty' .lisa.config.json 2>/dev/null)
[ -n "$_cfg" ] && REVIEW="$_cfg"
fi
if [ -f .lisa.config.local.json ]; then
_local=$(jq -r '.jira.workflow.review // .jira.workflow.code_review // empty' .lisa.config.local.json 2>/dev/null)
[ -n "$_local" ] && REVIEW="$_local"
fi
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:
NN-name.txtorNN-name.jsontext evidence files (e.g.,01-health-check.json)comment.txt— JIRA wiki markup (generated bygenerate-templates.py)comment.md— GitHub markdown (generated bygenerate-templates.py)
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 - Upload to GitHub
pr-assetsrelease — Uploads evidence files viagh release upload --clobber - Update PR description — Replaces or appends the
## Evidencesection in the PR body - Post JIRA comment — Posts
comment.txtas a new comment (wiki markup with code blocks) - Move ticket to the configured review status — Transitions the JIRA ticket to
$REVIEW(default:Code Review).
Evidence Naming Convention
Text evidence files are named: {NN}-{evidence-name}.txt or {NN}-{evidence-name}.json
evidence/
01-health-check.json uploaded
02-schema-after-migration.txt uploaded
03-rate-limit-response.txt uploaded
comment.txt used for JIRA comment
comment.md used for PR description
Troubleshooting
Evidence not appearing in GitHub PR
Evidence files must be in the pr-assets GitHub release. If the release does not exist:
gh release create pr-assets --title "PR Assets" --notes "CDN for PR evidence"
JIRA API returns 403
Ensure JIRA_API_TOKEN is set and login in ~/.config/.jira/.config.yml matches your Atlassian account email.
Related Skills
codyswanngt/plugins/src/harper-fabric/skills/harper-realtime
tools
VerifiedTrustedCommunity
--- name: harper-realtime description: This skill should be used when adding or troubleshooting Harper (HarperDB/Fabric) real-time behavior: MQTT topics, WebSocket resource subscriptions, resource publish/subscribe handlers, SSE-style streaming routes, and local subscriber verification. Pairs with harper-resources, harper-config-yaml, harper-schema-graphql, and harper-build-and-deploy. --- # Harper Realtime ## Overview Harper exposes live data through the same Resource model used for REST and
1SKILL.mdUpdated Jun 13, 2026
codyswanngt/plugins/lisa-harper-fabric/skills/harper-realtime
tools
VerifiedTrustedCommunity
--- name: harper-realtime description: This skill should be used when adding or troubleshooting Harper (HarperDB/Fabric) real-time behavior: MQTT topics, WebSocket resource subscriptions, resource publish/subscribe handlers, SSE-style streaming routes, and local subscriber verification. Pairs with harper-resources, harper-config-yaml, harper-schema-graphql, and harper-build-and-deploy. --- # Harper Realtime ## Overview Harper exposes live data through the same Resource model used for REST and
1SKILL.mdUpdated Jun 13, 2026
codyswanngt/plugins/lisa-harper-fabric-cursor/skills/harper-realtime
tools
VerifiedTrustedCommunity
--- name: harper-realtime description: This skill should be used when adding or troubleshooting Harper (HarperDB/Fabric) real-time behavior: MQTT topics, WebSocket resource subscriptions, resource publish/subscribe handlers, SSE-style streaming routes, and local subscriber verification. Pairs with harper-resources, harper-config-yaml, harper-schema-graphql, and harper-build-and-deploy. --- # Harper Realtime ## Overview Harper exposes live data through the same Resource model used for REST and
1SKILL.mdUpdated Jun 13, 2026
codyswanngt/plugins/lisa-harper-fabric-copilot/skills/harper-realtime
tools
VerifiedTrustedCommunity
--- name: harper-realtime description: This skill should be used when adding or troubleshooting Harper (HarperDB/Fabric) real-time behavior: MQTT topics, WebSocket resource subscriptions, resource publish/subscribe handlers, SSE-style streaming routes, and local subscriber verification. Pairs with harper-resources, harper-config-yaml, harper-schema-graphql, and harper-build-and-deploy. --- # Harper Realtime ## Overview Harper exposes live data through the same Resource model used for REST and
1SKILL.mdUpdated Jun 13, 2026