batch SKILL.md skillB
batch from mulhamna/jira-commands is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add mulhamna/jira-commands/batch@git:20260428.3a23448Pins 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/batch/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260428.3a23448, committed Apr 28, 2026
- Size
- 1,422 bytes
- Repository stars
- 54
- License
- a license file GitHub does not identify
Run mixed Jira operations (create, update, transition, archive) from a single JSON manifest file using jirac batch.
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
Run mixed Jira operations in batch 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. Build a JSON manifest array from the user's request. Each object needs an `"op"` field:
- `"create"` — same fields as bulk-create manifest (`project`, `summary`, `type`, etc.)
- `"update"` — `key` + fields to update (`summary`, `priority`, `assignee`, etc.)
- `"transition"` — `key` + `to` (transition name or ID)
- `"archive"` — `key`
3. Save the manifest to a temp file (e.g. `/tmp/ops.json`).
4. Run `jirac issue batch --manifest /tmp/ops.json`.
5. Report the per-op result summary.
Manifest format:
```json
[
{ "op": "create", "project": "PROJ", "summary": "New task", "type": "Task" },
{ "op": "update", "key": "PROJ-10", "priority": "High", "assignee": "me" },
{ "op": "transition", "key": "PROJ-11", "to": "Done" },
{ "op": "archive", "key": "PROJ-12" }
]
```
Examples:
- "create a task and close two other issues in one go" → build batch manifest, run `jirac issue batch --manifest /tmp/ops.json`
…Read the whole file at its exact version.
How to install
mdr add mulhamna/jira-commands/batch@sha256:cd0ce47ea4690c71The 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.
[](https://markdownregistry.com/a/art_oawr3cyf4cvhno4a)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Apr 28, 2026.
Audit of the latest version
- fail: Frontmatter declares a name
- pass: Frontmatter block present
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (1422 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
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_oawr3cyf4cvhno4a GET https://markdownregistry.com/api/v1/resolve?ref=mulhamna/jira-commands/batch GET https://markdownregistry.com/api/v1/blob/cd0ce47ea4690c71ace3cc72efce2d3d7b40e8d4ab1aef0de10a40e78ba9e9dc
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
Every file in mulhamna/jira-commands