jira-update

Apply guarded JIRA comments, workflow transitions, and tester assignment after a completed fix.

1|Updated May 15, 2026
One-click install
npx skills add https://github.com/c2kaka/fancy-skills --skill jira-update-c2kaka
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: jira-update
Source: https://github.com/c2kaka/fancy-skills/tree/main/skills/jira-update
Command: npx skills add https://github.com/c2kaka/fancy-skills --skill jira-update-c2kaka

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? After fixing a JIRA bug, engineers still need to write the repair comment, move the issue through the project workflow to testing, and assign the tester—operations that are non-transactional and risky to automate. This Skill performs those JIRA REST writes only after explicit user confirmation and safely recovers from partial updates. ## Core Features & Use Cases - Read-only inspection first: Fetches the issue's current status, reporter, assignee, and available transitions via GET requests before any write occurs. - Confirmation-gated writes: Drafts a structured repair comment from a template, presents the full transition plan and tester in one confirmation packet, and writes nothing until the user approves. - Partial-update recovery: Detects which steps completed when a write fails mid-operation and resumes the remaining transitions without duplicating the comment. - Use Case: After finishing a WARP project bug fix with jira-auto-fix, run this Skill to post the approved repair comment, transition the issue through Start Process, Start Review, and Start Test to the TEST status, and assign the reporter as tester. ## Quick Start Use the jira-update skill to inspect issue WARP-1234, preview the repair comment and transition plan to TEST with the reporter as tester, and apply it after my confirmation.

Frequently Asked Questions about jira-update

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I transition a JIRA issue to testing after a bug fix?▼

Run the inspect command to read the issue's available transitions, confirm the comment, transition plan, and tester in one approval packet, then run the apply command. The script executes the confirmed transitions in order and assigns the tester last.

How do I update a JIRA issue using the REST API from Python?▼

Use the jira_update.py script with Basic authentication from a local .env file. It calls the JIRA REST API endpoints for comments, transitions, and assignee updates, with a --confirm flag that must match the issue key before any write executes.

What happens if a JIRA update fails partway through?▼

The script raises a PartialUpdateError listing completed steps and the failed step, then stops without retrying. After re-inspecting the issue, you can run the resume command to continue remaining transitions without duplicating an already-posted comment.

Does this JIRA skill write anything without my approval?▼

No. All comments, transitions, and assignments are treated as external writes and require explicit confirmation of the exact comment text, transition IDs, final status, and tester username. Inspection uses GET requests only.

Where are JIRA credentials stored for this skill?▼

Credentials live in a skill-local .env file containing JIRA_BASE_URL, JIRA_USER, and JIRA_PASSWORD, copied from .env.example. The file is git-ignored, never printed, and credentials are never requested through chat.