@mulhamna/create-issue
BCreate new Jira issues with jirac, including interactive prompts for project, issue type, summary, and custom fields
Install
agr install @mulhamna/create-issue --target claudeWrites 1 file into .claude/skills/, pinned to git-656a4f36.
- .claude/skills/create-issue/SKILL.md
Document
description: Create new Jira issues with jirac, including interactive prompts for project, issue type, summary, and custom fields
Create a new Jira issue using jirac.
Steps:
- Check that
jiracis available by runningjirac --version. If it is missing, tell the user to install it withcargo install jira-commands. - Extract from the user's request:
- project key
- issue type
- summary
- any explicit assignee, labels, priority, parent, or other fields
- 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-versions,--description-file <FILE>--field <ID=VALUE>for custom fields (repeatable)--no-custom-fieldsto skip required custom field prompts
- Run
jirac issue createwith the fields that are already known. - Let
jiracprompt for any missing required fields. - If custom fields are unclear, run
jirac issue fields -p <PROJECT> --issue-type '<TYPE>'first. - Confirm the created issue key clearly.
Examples:
- "create an issue in PROJ" →
jirac issue create -p PROJ - "create a bug in PROJ called login page crashes" →
jirac issue create -p PROJ -t Bug -s 'login page crashes' - "create sub-task under PROJ-100" →
jirac issue create -p PROJ -t Sub-task -s 'sub-task title' --parent PROJ-100 - "create story in Sprint 24" →
jirac issue create -p PROJ -t Story -s 'story title' --sprint 'Sprint 24' - "create with story points 5" →
jirac issue create -p PROJ -t Story -s 'title' --field story_points=5 - "buat task baru di PROJ" →
jirac issue create -p PROJ -t Task
Trustgrade B
- passBody integrity
Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.
- passType matchnot applicable to this artifact type
Whether the artifact is really the kind of thing its metadata claims it is.
- passFreshness
How long since the source repository was last pushed to.
- passPrompt injection
Scans the artifact's own text for instructions aimed at your agent rather than at you.
- warnLicenseno SPDX license detected
Whether the source repository declares an SPDX license permissive enough to redistribute.
How the grade is calculated
Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:
- Aevery check passed
- Bone warning
- Ctwo warnings
- Dprompt injection or body integrity failed, or three warnings
- Fone of those failed, and something else is wrong
These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.
Versions
git-656a4f36a09e2026-07-31