Menu
Manage JIRA tickets. Use it when the user mentions JIRA with ticket IDs like FOO-123.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when querying Elasticsearch through the Kibana console proxy, especially for log investigations, field-based filtering, or error triage from job or application logs.
Use when pressure-testing a plan, architecture, code change, or AI-generated proposal before committing, especially when hidden assumptions, production risks, or failure modes may be underexplored.
Use when creating or updating skills in `~/.config/ai/skills`, especially when a `SKILL.md` has a weak trigger, tangled structure, poor steering, or bloated wording.
Use when interacting with Datadog resources using the `pup` CLI, especially for APM traces, metrics, monitors, notebooks, and synthetic tests.
Use when simplifying recently touched code without changing behavior, especially when asked to "simplify code", "clean up code", "refactor for clarity", or "improve readability".
Ingest a URL into the patient account wiki. Use when the user provides a URL (Atlassian/Confluence, web articles, documentation) and wants to add it to their research wiki. Handles fetching, markdown conversion, asset extraction, and runs the full wiki ingest workflow. Triggers on "ingest <url>", "add this to the wiki", or when user shares a URL in the context of wiki research.
| name | jira |
| description | Manage JIRA tickets. Use it when the user mentions JIRA with ticket IDs like FOO-123. |
You are a Jira CLI expert assistant using jira-cli.
jira issue view ISSUE-KEY [--comments N]
--comments 5 to see recent comments--raw to get raw JSON responsejira issue edit ISSUE-KEY -s"New Title" -b"New Description" [--no-input]
-s, --summary - Change issue title-b, --body - Change issue description--no-input - Skip interactive promptsecho "Description" | jira issue edit ISSUE-KEY --no-inputjira issue comment add ISSUE-KEY "Comment text"
jira issue comment add ISSUE-KEY "My comment"jira issue comment add ISSUE-KEY $'Line 1\n\nLine 2'jira issue comment add ISSUE-KEY --template /path/to/fileecho "Comment" | jira issue comment add ISSUE-KEYjira issue move ISSUE-KEY "State Name"
Available states:
"To Do""In progress""To be reviewed""To be validated""Done"Examples:
jira issue move ISSUE-1 "In progress"
jira issue move ISSUE-1 Done --comment "Completed"
jira issue view to check current state before editing"In progress")jira issue view <key>jira me--debug flag for troubleshooting