Menú
Make Jira Cloud REST API requests via a local helper script using credentials from environment variables or macOS Keychain. Use by default for Jira work: reading, searching, updating tickets, JQL, comments, transitions, ADF payloads, or any request involving Jira issues.
Perform grounded, broad code reviews that avoid tunnel vision and low-value findings. Use when asked to review code, changes, diffs, staged/unstaged work, branches, pull requests, or architecture impact of a change.
Ground agent hypotheses in verifiable evidence from source code, docs, issues, and concrete citations before acting. Use when investigating bugs, library behavior, architecture questions, ambiguous errors, or any task where guessing, assumptions, or stale knowledge could lead to wrong changes.
Create or Update Pull Request on Github
Save important information from the current agent conversation into a human-readable Markdown document. Use when the user invokes /save-to-md, asks to save an investigation/decision/summary to an .md file, or wants conversation context captured as documentation or an ADR-like record.
Investigate bugs/issues to find concrete, evidence-backed reproduction steps without fixing them. Use when the user reports a bug, failure, regression, flaky behavior, stack trace, unexpected output, or asks to debug/reproduce an issue.
Use jj (Jujutsu) for local version control instead of git. Activate when: the repo has a .jj/ directory, the user or project config mentions jj, the user says 'use jj', or any version control operation is needed in a jj-managed repo. Also use this skill when the user asks to commit, branch, stash, rebase, or perform any git-like operation in a repo that uses jj. If unsure whether the repo uses jj, check for a .jj/ directory.
| name | jira-api |
| description | Make Jira Cloud REST API requests via a local helper script using credentials from environment variables or macOS Keychain. Use by default for Jira work: reading, searching, updating tickets, JQL, comments, transitions, ADF payloads, or any request involving Jira issues. |
Use the helper script by default for Jira work.
node >= 18 on PATH.JIRA_BASE_URL or ATLASSIAN_SITE_URL (example: https://example.atlassian.net)JIRA_EMAIL or ATLASSIAN_EMAILJIRA_API_TOKEN or ATLASSIAN_API_TOKENKeychain setup examples:
security add-generic-password -a "$USER" -s JIRA_BASE_URL -w 'https://example.atlassian.net'
security add-generic-password -a "$USER" -s JIRA_EMAIL -w 'me@example.com'
security add-generic-password -a 'me@example.com' -s JIRA_API_TOKEN -w 'TOKEN'
The helper script lives in the same directory as this SKILL.md file (scripts/jira.mjs).
Resolve it against the skill directory — do not search the repo. Use it directly:
node <skill-dir>/scripts/jira.mjs <command> ...
The script emits JSON and exits non-zero on hard errors.
Common commands:
node <skill-dir>/scripts/jira.mjs me
node <skill-dir>/scripts/jira.mjs projects [query]
node <skill-dir>/scripts/jira.mjs issue ABC-123
node <skill-dir>/scripts/jira.mjs comments ABC-123
node <skill-dir>/scripts/jira.mjs search 'project = ABC AND statusCategory != Done ORDER BY updated DESC' 'summary,status,assignee'
node <skill-dir>/scripts/jira.mjs transitions ABC-123
node <skill-dir>/scripts/jira.mjs transition ABC-123 31
node <skill-dir>/scripts/jira.mjs add-comment ABC-123 'Plain text comment'
echo '{"fields":{"summary":"New summary"}}' | node <skill-dir>/scripts/jira.mjs edit ABC-123
node <skill-dir>/scripts/jira.mjs request GET /rest/api/3/issue/ABC-123 # raw escape hatch
issue <KEY> for compact issue details with plain-text description.comments <KEY> if comment context matters.transitions <KEY> before changing status.add-comment <KEY> <text> creates valid ADF.edit <KEY> reads raw Jira JSON from stdin.request METHOD PATH [json].edit or request./rest/api/3/search/jql for JQL search; pagination uses nextPageToken.