narumiruna/using-jira-cli
skills/workflow-repository/using-jira-cli/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add narumiruna/agent-skills using-jira-cliInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jul 23, 2026, 6:33 AM146.8s3 files scanned
SKILL.md
- name:
- using-jira-cli
- description:
- 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.
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
- Check
command -v jira,jira version, andjira mewithout exposing token values. - Identify the Jira instance and config file before querying or mutating. For multiple configs, use the confirmed
JIRA_CONFIG_FILEor-cpath consistently. - If setup is missing, do not run interactive
jira initin an agent shell. Ask the user to complete it or follow a verified non-interactive setup path. UseJIRA_API_TOKEN,.netrc, keychain, or existing secure configuration; never print, persist, or place secrets in command arguments. - Read installed help for version-sensitive syntax:
jira --help, thenjira <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
- Read the current target and discover valid field/status values.
- 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.
- 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.
- 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.
- 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.
Related Skills
narumiruna/scoring-agent-skills
development
VerifiedTrustedCommunity
Score or compare one or more agent skills across trigger clarity, workflow actionability, safety boundaries, verification rigor, incremental knowledge value, and leanness. Use only when the user explicitly asks for ratings, numerical quality scores, rubric-based scorecards, or scored comparisons; use creating-agent-skills for unscored reviews or revisions.
8SKILL.mdUpdated Jul 29, 2026
narumiruna/improving-codebase-architecture
development
VerifiedTrustedCommunity
Assess or improve an existing codebase's architecture when the user asks about module boundaries, coupling, scattered ownership, testability, change locality, deep modules, seams, or behavior-preserving structural refactoring. Use for cross-module design rather than ordinary diff review or a confirmed edge-case bug fix.
8SKILL.mdUpdated Jul 29, 2026
narumiruna/auditing-code-security
development
VerifiedTrustedCommunity
Perform read-only security audits, vulnerability assessments, or threat-focused reviews of diffs, pull requests, code paths, or explicitly scoped repositories when security is the primary objective or acceptance criterion. Use reviewing-code for ordinary review with baseline security coverage and hardening-code-paths for fixing confirmed findings.
8SKILL.mdUpdated Jul 29, 2026
narumiruna/running-panel-review-loops
development
VerifiedTrustedCommunity
Run iterative multi-reviewer panels over a code diff, verify their findings, apply explicitly authorized fixes, and re-review the updated change until it passes or reaches a stopping condition. Use when the user asks for a panel loop, multi-model code-review consensus, or a review-fix-re-review cycle.
8SKILL.mdUpdated Jul 26, 2026