change-type SKILL.md skillB
change-type 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/change-type@git:20260521.f34ad5ePins git:20260521.f34ad5e 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/change-type/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260521.f34ad5e, committed May 21, 2026
- Size
- 1,233 bytes
- Repository stars
- 54
- License
- a license file GitHub does not identify
Change a Jira issue to another issue type using Jira's native move semantics with jirac.
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
Change an issue's type (e.g. Bug → Story) using `jirac`. This uses Jira's native move semantics — the issue key is preserved. Steps: 1. Check that `jirac` is available by running `jirac --version`. If missing, tell the user to install it (`cargo install jira-commands`). 2. Extract from the user's request: - issue key - target issue type name (e.g. Bug, Story, Task, Sub-task) 3. Confirm intent — type changes can affect required fields and screens. 4. Run `jirac issue change-type <KEY> <TYPE>`. 5. Report the updated issue and its new type. Use `jirac issue view <KEY>` if confirmation is needed. Notes: - Issue key is **preserved** (PROJ-123 stays PROJ-123). - Some custom-field values may be dropped if the new type's screen excludes them — verify with `jirac issue fields -p PROJ --issue-type <TYPE>` beforehand. - Use `jirac issue move` instead when moving across **projects**; use `change-type` when staying in the same project. Examples: - "change PROJ-123 to a Bug" → `jirac issue change-type PROJ-123 Bug` - "convert PROJ-50 from Sub-task to Story" → `jirac issue change-type PROJ-50 Story`
Read the whole file at its exact version.
How to install
mdr add mulhamna/jira-commands/change-type@sha256:e8ff208ba72bd032The line at the top of this page pins the label git:20260521.f34ad5e, 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_3ndn5eg5ojjificc)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on May 21, 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 (1233 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_3ndn5eg5ojjificc GET https://markdownregistry.com/api/v1/resolve?ref=mulhamna/jira-commands/change-type GET https://markdownregistry.com/api/v1/blob/e8ff208ba72bd03289cd685131823b7d374e9f05701b201177805d105a90627e
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.