About jira-fix-batch
jira-fix-batch is a trigger skill for batch Jira fix requests, intended for workflows that enqueue Jira items for processing. It parses Jira IDs or URLs and hands them to goal-driven-batch with jira-fix-workflow fixed, without starting queue consumption.
Key features
- 01Parse multiple Jira IDs or URLs
- 02Enqueue through goal-driven-batch
- 03Fix the repair engine for each card
- 04Activate only for explicit batch-fix requests
- 05Stop after enqueueing; do not consume the queue
Use cases
- 01Enqueue a set of Jira bugs for batch processing
- 02Set one workflow for a batch of fix requests
Install
Copy the command and run it in a terminal.
npx skills add https:/After installing, type/jira-fix-batchin Claude Code to confirm it loaded.
Details
From the project READMEJira Bug Batch Enqueue Shell
Trigger-only shell. Queue lifecycle, relationship pass, isolation, caps, and acceptance live in
goal-driven-batch. This skill parses a Jira list and hands it to that skill's Jira list-enqueue shortcut withEngine: jira-fix-workflowalready frozen.
Activate only when the user explicitly requests a batch Jira fix. Loading this skill MUST NOT start a queue run.
Prerequisite Skill Check
Scan available skills. If goal-driven-batch is missing, abort immediately with install guidance (npx skills add FuDesign2008/open-skills -g --skill goal-driven-batch --yes). No silent fallback — without the queue there is no place to put the cards.
Duties
- Split the input into distinct Jira IDs/URLs.
- Load
goal-driven-batchand run its Jira list-enqueue shortcut withEngine: jira-fix-workflowfrozen on every card. - Stop when that shortcut stops (cards written, one batch approval event). Do not start consumption. Do not call
jira-fix-workflow. Do not write.jira-fix/progress files.
Red Flags
- Looping
jira-fix-workflowfrom this skill - Starting the queue because the list was parsed
- Re-implementing relationship detection, mode propagation, or a progress document here