create-issue SKILL.md skillB
create-issue 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/create-issue@git:20261029.f79e226Pins git:20261029.f79e226 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/create-issue/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261029.f79e226, committed Oct 29, 2026
- First version recorded
- Apr 15, 2026
- Size
- 1,787 bytes
- Repository stars
- 54
- License
- a license file GitHub does not identify
Create new Jira issues with jirac, including interactive prompts for project, issue type, summary, and custom fields.
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
Create a new Jira issue 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 - issue type - summary - any explicit assignee, labels, priority, parent, or other fields 3. Map the request to supported flags: - `-p / --project`, `-s / --summary`, `-t / --issue-type` - `--assignee` (email or "me"), `--priority`, `--labels`, `--components` - `--parent <ISSUE-KEY>` for sub-tasks - `--sprint <ID|NAME>` to assign to a sprint on create - `--fix-version`, `--description-file <FILE>` - `--field <ID=VALUE>` for custom fields (repeatable) - `--no-custom-fields` to skip required custom field prompts 4. Run `jirac issue create` with the fields that are already known. 5. Let `jirac` prompt for any missing required fields. 6. If custom fields are unclear, run `jirac issue fields -p <PROJECT> --issue-type '<TYPE>'` first. 7. Confirm the created issue key clearly. Examples: - "create an issue in PROJ" → `jirac issue create -p PROJ` …
Read the whole file at its exact version.
How to install
mdr add mulhamna/jira-commands/create-issue@sha256:8e054db24cc38d18The line at the top of this page pins the label git:20261029.f79e226, 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_z6w6uio2uztbazn2)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Apr 15, 2026 and Oct 29, 2026, about one every 49 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261029.f79e226 latest | 2026-10-29 | f79e226 | 1,787 B | B | view · diff |
| git:20260428.3a23448 | 2026-04-28 | 3a23448 | 1,788 B | B | view · diff |
| git:20260420.281fd3a | 2026-04-20 | 281fd3a | 1,020 B | B | view · diff |
| git:20260418.e640726 | 2026-04-18 | e640726 | 1,130 B | B | view · diff |
| git:20260415.2d33454 | 2026-04-15 | 2d33454 | 1,105 B | B | view |
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 (1787 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_z6w6uio2uztbazn2 GET https://markdownregistry.com/api/v1/resolve?ref=mulhamna/jira-commands/create-issue GET https://markdownregistry.com/api/v1/blob/8e054db24cc38d18877e253890a4efcfaeb7c80b9c2a7ab595afaca5a1cba9be
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