agentleFS
Sign inStart free
FuDesign2008FuDesign2008/open-skills/skills/opsx-jira-fix-queue/SKILL.md

opsx-jira-fix-queue

Skill6 starsChanged 6 days agoMITView on GitHub

Triggers when the user says「opsx 批量修复」「批量 opsx-jira-fix」「opsx-jira-fix-queue」「opsx-jira-fix-batch」「批量 OpenSpec Jira 修复」/ opsx batch fix, batch OpenSpec Jira fix, opsx-jira-fix-queue, opsx-jira-fix-batch. Thin trigger shell: parse Jira IDs/URLs and enqueue them into goal-driven-queue with Engine opsx-jira-fix-workflow. Does not run fixes or merge. Do NOT use for a single issue (opsx-jira-fix-workflow) or a non-Jira queue (goal-driven-queue).

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Stop when that shortcut stops (cards written, one batch approval event).

    line 28

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

OPSX Jira Bug Queue Enqueue Shell

Trigger-only shell. Queue lifecycle, relationship pass, isolation, caps, and acceptance live in goal-driven-queue. 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-queue is missing, abort immediately with install guidance (npx skills add FuDesign2008/open-skills -g --skill goal-driven-queue --yes). No silent fallback.

Duties

  1. Split the input into distinct Jira IDs/URLs.
  2. Load goal-driven-queue 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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free