bulk-transition SKILL.md skillB

bulk-transition from mulhamna/jira-commands is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add mulhamna/jira-commands/bulk-transition@git:20260428.3a23448

Pins git:20260428.3a23448 in mdr.lock. Pin the fingerprint instead.

Audit grade
B, 16 of 17 checks passed
Kind
SKILL.md skill
Repository
mulhamna/jira-commands
Path
plugin/skills/bulk-transition/SKILL.md
Versions recorded
4
Latest version
git:20260428.3a23448, committed Apr 28, 2026
First version recorded
Apr 15, 2026
Size
1,214 bytes
Repository stars
54
License
a license file GitHub does not identify

Bulk transition multiple Jira issues with a JQL filter through the jirac CLI.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

Bulk transition multiple Jira issues using `jirac`.

Steps:
1. Check that `jirac` is available by running `jirac --version`. If it is missing, tell the user to install it with `cargo install jira-commands`.
2. Extract from the user's request:
   - project key when relevant
   - target status
   - JQL filter, or enough context to build one
   - whether the user wants to skip confirmation
3. If no JQL is provided, build one from the request, for example `project = PROJ AND status = "To Do"`.
4. Run `jirac issue bulk-transition --jql '<JQL>' --to '<STATUS>' [--force]`.
5. Make it clear how many issues are affected and whether confirmation is still required.

Examples:
- "transition all To Do issues in PROJ to In Progress" → `jirac issue bulk-transition --jql 'project = PROJ AND status = "To Do"' --to 'In Progress'`
- "close all done issues in PROJ without asking" → `jirac issue bulk-transition --jql 'project = PROJ AND status = Done' --to 'Closed' --force`
- "move my open sprint issues to Done" → `jirac issue bulk-transition --jql 'assignee = currentUser() AND sprint = openSprints()' --to Done`

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint
mdr add mulhamna/jira-commands/bulk-transition@sha256:bcfc96d228bf8908

The line at the top of this page pins the label git:20260428.3a23448, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_axbomm6tehibhprc.svg)](https://markdownregistry.com/a/art_axbomm6tehibhprc)

0 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 4 versions of this file, between Apr 15, 2026 and Apr 28, 2026, about one every 4 days.

versioncommittedcommitsizeaudit
git:20260428.3a23448 latest2026-04-28 3a23448 1,214 BB view · diff
git:20260420.281fd3a2026-04-20 281fd3a 1,085 BB view · diff
git:20260418.e6407262026-04-18 e640726 1,215 BB view · diff
git:20260415.2d334542026-04-15 2d33454 1,191 BB view

Audit of the latest version

B  16 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • fail: Frontmatter declares a name
  • pass: Frontmatter block present
  • pass: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (1214 bytes)
  • pass: No zero-width or bidi control characters
  • pass: No instruction hidden inside an HTML comment
  • pass: No link to an exfiltration or paste host
  • pass: No credential-shaped string
  • pass: No instruction to send local credentials anywhere
  • pass: No text hidden with inline styles
  • pass: No prompt-injection phrasing
  • pass: No curl or wget piped into a shell
  • pass: No recursive delete of root, home or parent
  • pass: No instruction to read or print local credentials
  • pass: No base64 blob over 200 characters
  • pass: No link to a raw IP address
  • pass: No script tag

Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.

Source

GitHub

mulhamna/jira-commands · 54 stars · license a license file GitHub does not identify · pushed 2026-10-31 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_axbomm6tehibhprc
GET https://markdownregistry.com/api/v1/resolve?ref=mulhamna/jira-commands/bulk-transition
GET https://markdownregistry.com/api/v1/blob/bcfc96d228bf8908617991b474f2508007a1531399be069c419dedf1618c4806

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from mulhamna/jira-commands

AGENTS.md AGENTS.md file
mulhamna/jira-commands · AGENTS.md
git:20260420.12a003d · audit A · 54 stars
CLAUDE.md CLAUDE.md file
mulhamna/jira-commands · CLAUDE.md
git:20260801.3784381 · audit A · 54 stars
jirac SKILL.md skill
mulhamna/jira-commands · clawhub/jirac/SKILL.md · Jira issue management skill for OpenClaw using the jirac CLI. Requires the `jirac` binary to be installed and…
git:20261029.f79e226 · audit A · 54 stars
api SKILL.md skill
mulhamna/jira-commands · plugin/skills/api/SKILL.md · Execute a raw Jira REST API call through the jirac CLI, including GET, POST, PUT, DELETE, and PATCH requests to any…
git:20260420.281fd3a · audit B · 54 stars
archive SKILL.md skill
mulhamna/jira-commands · plugin/skills/archive/SKILL.md · Archive Jira issues matching a JQL query with jirac
git:20260521.f34ad5e · audit B · 54 stars
attach SKILL.md skill
mulhamna/jira-commands · plugin/skills/attach/SKILL.md · Upload local files as Jira issue attachments through the jirac CLI
git:20260420.281fd3a · audit B · 54 stars
batch SKILL.md skill
mulhamna/jira-commands · plugin/skills/batch/SKILL.md · Run mixed Jira operations (create, update, transition, archive) from a single JSON manifest file using jirac batch
git:20260428.3a23448 · audit B · 54 stars
bulk-comment SKILL.md skill
mulhamna/jira-commands · plugin/skills/bulk-comment/SKILL.md · Add the same Markdown comment to multiple Jira issues with jirac, either by JQL query or explicit issue keys
git:20260516.4a5a915 · audit B · 54 stars
bulk-create SKILL.md skill
mulhamna/jira-commands · plugin/skills/bulk-create/SKILL.md · Create multiple Jira issues at once from a JSON manifest file using jirac bulk-create
git:20260428.3a23448 · audit B · 54 stars
bulk-update SKILL.md skill
mulhamna/jira-commands · plugin/skills/bulk-update/SKILL.md · Bulk update assignee or priority on multiple Jira issues matching a JQL query with jirac
git:20260428.3a23448 · audit B · 54 stars
change-type SKILL.md skill
mulhamna/jira-commands · plugin/skills/change-type/SKILL.md · Change a Jira issue to another issue type using Jira's native move semantics with jirac
git:20260521.f34ad5e · audit B · 54 stars
clone-issue SKILL.md skill
mulhamna/jira-commands · plugin/skills/clone-issue/SKILL.md · Clone a Jira issue with jirac, optionally into another project or with a new summary and assignee
git:20260428.3a23448 · audit B · 54 stars

Every file in mulhamna/jira-commands

Browse by kind, by grade B, or by owner.