OpenParable
Skip to content
← Back to skills

Jira Evidence

Productivity
jira-evidence

Jira Evidence is an Agent Skill for productivity published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

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.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/integration/jira-evidence-codyswanngt-lisa/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/jira-evidence, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

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:
    • Evidence files: NN-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)

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

  1. Read JIRA config — Reads ~/.config/.jira/.config.yml to obtain server and login dynamically (no hardcoded values)
  2. Upload to GitHub pr-assets release — Uploads evidence files via gh release upload --clobber, creating CDN URLs
  3. Update PR description — Replaces or appends the ## Evidence section in the PR body using gh pr edit
  4. Upload JIRA attachments — Uploads image evidence via REST API v3 so !filename.png! wiki markup renders inline
  5. Post JIRA comment — Posts comment.txt as a new comment via REST API v2 (wiki markup)
  6. Move ticket to Code Review — Transitions the JIRA ticket via jira issue move

Evidence Naming Conventions

  • Image evidence: NN-name-viewport.png (e.g., 01-search-step-desktop.png)
  • Text evidence: NN-name.txt or NN-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 ~/.config/.jira/.config.yml matches your Atlassian account email.