How do I install the Jira Evidence skill?

Run npx skillmds@latest add majiayu000/jira-evidence in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Jira Evidence safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Jira Evidence?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Jira Evidence free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Jira Evidence?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Jira Evidence by majiayu000 — Agent Skill

Name: Jira Evidence
Rating: 4.2 (5 reviews)
Author: majiayu000

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.

majiayu000 Updated Sep 9, 2026 567 repo stars

File contents

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_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.

---name: jira-evidencedescription: 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.--- # 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_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 bash .claude/skills/jira-evidence/scripts/post-evidence.sh <TICKET_ID> <EVIDENCE_DIR> <PR_NUMBER> ``` ### Example ```bash bash .claude/skills/jira-evidence/scripts/post-evidence.sh PROJ-123 ./evidence 42 ``` ## What It Does 1. **Read JIRA config** — Reads `~/.config/.jira/.config.yml` to obtain `server` and `login` dynamically 2. **Upload to GitHub `pr-assets` release** — Uploads evidence files via `gh release upload --clobber` 3. **Update PR description** — Replaces or appends the `## Evidence` section in the PR body 4. **Post JIRA comment** — Posts `comment.txt` as a new comment (wiki markup with code blocks) 5. **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` ```text 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: ```bash 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.

Frequently asked questions