SkillsAdd

narumiruna/skills

using-jira-cli

Inspect Jira or prepare and perform precisely authorized Jira mutations with ankitpokhrel/jira-cli (`jira`), including issues, comments, worklogs, epics, sprints, releases, projects, boards, and script-friendly output.

First seen Jul 4, 2026

Installation

$ npx skills add narumiruna/skills --skill using-jira-cli
View on skills.sh ↗ GitHub repository ↗

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

creating-secrets-using-best-practices Similar name
aws/agent-toolkit-for-aws

Creates and manages secrets in AWS Secrets Manager following security best practices. Always us…

5K installs
using-n8n-skills-official Similar name
n8n-io/skills

Use when working with n8n workflows in any capacity.

1.2K installs
using-medusa-cloud Similar name
medusajs/medusa-agent-skills

Manages Medusa Cloud resources through the Cloud CLI (mcloud). Use when deploying, debugging de…

10 installs
using-dbt-for-analytics-engineering Similar name
dbt-labs/dbt-agent-skills

Builds and modifies dbt models, writes SQL transformations using ref() and source(), creates te…

902 installs
using-superpowers Similar name
obra/superpowers

Use when starting any conversation - establishes how to find and use skills, requiring skill in…

238.2K installs
using-git-worktrees Similar name
obra/superpowers

Use when starting feature work that needs isolation from current workspace or before executing …

184.6K installs

Also in this package

Other skills from narumiruna/skills · top by installs.

npx skills add narumiruna/skills
svg-illustration 645 creating-svg-illustrations 232 writing-plans 75 writing-agents-md 48 reviewing-code 45 python-cli-typer 40 grilling-designs 39 applying-tdd 38 explaining-step-by-step 37 writing-git-commits 36

Browse all from narumiruna/skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 13
License LICENSE
Default branch main
Open issues 0
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,984 B
  • docs SUMMARY.md 240 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 24 installs

SKILL.md

Using Jira CLI

Use read-only discovery freely. Jira creates, edits, transitions, assignments, comments, worklogs, links, sprint/epic changes, and deletes are external writes and require authorization for the exact operation, target, and content. Supplying values for a draft does not authorize execution.

Establish Context

  1. Check command -v jira, jira version, and jira me without exposing token values.
  2. Identify the Jira instance and config file before querying or mutating. For multiple configs, use the confirmed JIRACONFIGFILE or -c path consistently.
  3. If setup is missing, do not run interactive jira init in an agent shell. Ask the user to complete it or follow a verified non-interactive setup path. Use JIRAAPITOKEN, .netrc, keychain, or existing secure configuration; never print, persist, or place secrets in command arguments.
  4. Read installed help for version-sensitive syntax: jira --help, then jira <resource> <command> --help.

Read Workflow

  • Discover project, board, user, status, field, or sprint context before assuming names or IDs.
  • Use explicit issue keys for detail views.
  • Prefer non-interactive, script-friendly output only when the installed command supports it: --plain, --raw, --csv, --no-headers, or --columns.
  • Avoid commands that open an interactive issue browser; add the supported plain/raw form or use a narrower view.

Read references/commands.md only for the relevant resource's common command shapes, then verify flags against installed help.

Mutation Workflow

  1. Read the current target and discover valid field/status values.
  2. Prepare the exact Jira instance/config, issue or container IDs, operation, summary/body/comment/worklog text, transition, assignment, and other changed fields. Do not impose a project-name summary prefix or description template unless the user or repository requires it.
  3. If the exact operation, target, and content have not already been explicitly authorized for execution, show the complete mutation and ask for approval. Treat requests to draft, explain, review, or prepare Jira content as read-only. Always require exact approval for deletion.
  4. After approval, use non-interactive flags only when every required parameter is known. Quote values and provide long content through a template or stdin rather than unsafe shell interpolation.
  5. Re-read the affected issue or resource and report its resulting key, status, assignee, fields, or comment/worklog evidence. A zero exit code alone is not sufficient verification.

Do not broaden one approved mutation into related edits. If Jira returns an unexpected prompt, target, schema, or permission requirement, stop without guessing.