mcpField
O
opsx-jira-fix-batch

opsx-jira-fix-batch

github.com/fudesign2008Agent workflows665 installsUpdated 1d ago
Repository

About opsx-jira-fix-batch

opsx-jira-fix-batch is a trigger-only skill for turning a list of Jira issues into queued cards for `goal-driven-batch`. It fixes `opsx-jira-fix-workflow` as the engine and stops after enqueueing, without starting queue consumption or writing OpenSpec artifacts.

Key features

  1. 01Parse Jira IDs and URLs
  2. 02Enqueue via `goal-driven-batch` shortcut
  3. 03Freeze `opsx-jira-fix-workflow` as engine
  4. 04Stop after batch approval event
  5. 05Require `goal-driven-batch` prerequisite

Use cases

  1. 01Queue several Jira issues for batch fixes
  2. 02Prepare cards without starting execution
  3. 03Route Jira fixes through a specified workflow

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/fudesign2008/open-skills --skill opsx-jira-fix-batch

After installing, type/opsx-jira-fix-batchin Claude Code to confirm it loaded.

Details

From the project README

OPSX Jira 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 with Engine: opsx-jira-fix-workflow already frozen.

Related-issue persistence in OpenSpec design.md is the child engine's job after dispatch (opsx-jira-fix-workflow receives relationship-pass notes in the card supply). This shell does not write OpenSpec artifacts.

Activate only when the user explicitly requests an OPSX 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.

Duties

  1. Split the input into distinct Jira IDs/URLs.
  2. Load goal-driven-batch and run its Jira list-enqueue shortcut with Engine: opsx-jira-fix-workflow frozen on every card.
  3. Stop when that shortcut stops (cards written, one batch approval event). Do not start consumption. Do not call opsx-jira-fix-workflow. Do not write a parallel progress file.

Red Flags

  • Looping opsx-jira-fix-workflow from this skill
  • Starting the queue because the list was parsed
  • Sharing one OpenSpec change or one branch across in-progress cards (the queue forbids that)
  • Re-implementing relationship detection here

Comments

Markdown supported