Skill

jira-evidence

Upload text evidence to GitHub pr-assets release, update PR description, post JIRA comment with code blocks, and move ticket to Code Review. Reusable by any skill that captures evidence and generates evidence/comment.txt + evidence/comment.md.

Install

npx claudepluginhub codyswanngt/lisa --plugin lisa

Tool Access

This skill uses the workspace's default tool permissions.

Preview

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.

Supporting Assets

scripts/post-evidence.sh

SKILL.md

Similar Skills

cache-components

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

139.2k

mcp-builder

9 files

Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).

anthropics-skills-13

124.2k

canvas-design

20 files

Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.

anthropics-skills-13

124.2k

Stats

Parent Repo Stars1

Parent Repo Forks2

Last CommitMar 5, 2026

Actions

View Source View Plugin View on GitHub View README

JIRA Evidence Posting

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_TOKEN environment variable set
jira-cli configured (~/.config/.jira/.config.yml) — server and login are read from there
gh CLI authenticated
Evidence directory containing:
- NN-name.txt or NN-name.json text evidence files (e.g., 01-health-check.json)
- comment.txt — JIRA wiki markup (generated by generate-templates.py)
- comment.md — GitHub markdown (generated by generate-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.yml to obtain server and login dynamically
Upload to GitHub pr-assets release — Uploads evidence files via gh release upload --clobber
Update PR description — Replaces or appends the ## Evidence section in the PR body
Post JIRA comment — Posts comment.txt as a new comment (wiki markup with code blocks)
Move ticket to Code Review — Transitions the JIRA ticket

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.