fields SKILL.md skillB

fields 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/fields@git:20260420.281fd3a

Pins git:20260420.281fd3a 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/fields/SKILL.md
Versions recorded
2
Latest version
git:20260420.281fd3a, committed Apr 20, 2026
First version recorded
Apr 20, 2026
Size
949 bytes
Repository stars
54
License
a license file GitHub does not identify

Inspect Jira field metadata with jirac for a project and issue type, especially before create or update flows that use custom fields or backlog-specific schemas.

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

List available Jira fields 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
   - optional issue type
   - whether they want only required fields
3. Run one of these:
   - `jirac issue fields -p <PROJECT>`
   - `jirac issue fields -p <PROJECT> --issue-type '<TYPE>'`
   - add `--required-only` when requested
4. Highlight the field IDs and likely value shapes that matter for the next step.

Examples:
- "show required fields for Story in PROJ" → `jirac issue fields -p PROJ --issue-type 'Story' --required-only`
- "what custom fields are available in PROJ" → `jirac issue fields -p PROJ`

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint
mdr add mulhamna/jira-commands/fields@sha256:716786371ca6a7b4

The line at the top of this page pins the label git:20260420.281fd3a, 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_owwms2u66qrntwut.svg)](https://markdownregistry.com/a/art_owwms2u66qrntwut)

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

Versions

The registry has recorded 2 versions of this file, all committed on Apr 20, 2026.

versioncommittedcommitsizeaudit
git:20260420.281fd3a latest2026-04-20 281fd3a 949 BB view · diff
git:20260420.19999482026-04-20 1999948 1,004 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 (949 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_owwms2u66qrntwut
GET https://markdownregistry.com/api/v1/resolve?ref=mulhamna/jira-commands/fields
GET https://markdownregistry.com/api/v1/blob/716786371ca6a7b4cdc05f3f7bdc6aa5882cd14164ffd1540cab05c8233b4c60

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-transition SKILL.md skill
mulhamna/jira-commands · plugin/skills/bulk-transition/SKILL.md · Bulk transition multiple Jira issues with a JQL filter through the jirac CLI
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

Every file in mulhamna/jira-commands

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