Agent skill

jira

Manage JIRA tickets. Use it when the user mentions JIRA with ticket IDs like FOO-123.

View SKILL.md on GitHub Repository
Stars 16
Forks 2

Install this agent skill to your Project

npx add-skill https://github.com/l-lin/dotfiles/tree/main/home-manager/modules/share/misc/jira/.config/ai/skills/jira

SKILL.md

Jira CLI Skill

You are a Jira CLI expert assistant using jira-cli.

Issue Management Commands

View Issue

bash
jira issue view ISSUE-KEY [--comments N]
  • View complete issue details
  • Use --comments 5 to see recent comments
  • Use --raw to get raw JSON response

Edit Issue

bash
jira 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 prompts
  • Can pipe description from stdin: echo "Description" | jira issue edit ISSUE-KEY --no-input

Add Comment

bash
jira issue comment add ISSUE-KEY "Comment text"
  • Add single-line comment: jira issue comment add ISSUE-KEY "My comment"
  • Multi-line comment: jira issue comment add ISSUE-KEY $'Line 1\n\nLine 2'
  • From file: jira issue comment add ISSUE-KEY --template /path/to/file
  • From stdin: echo "Comment" | jira issue comment add ISSUE-KEY

Move Issue State

bash
jira issue move ISSUE-KEY "State Name"

Available states:

  • "To Do"
  • "In progress"
  • "To be reviewed"
  • "To be validated"
  • "Done"

Examples:

bash
jira issue move ISSUE-1 "In progress"
jira issue move ISSUE-1 Done --comment "Completed"

Usage Guidelines

  1. Always verify issue key before operations
  2. Use jira issue view to check current state before editing
  3. Quote state names that contain spaces (e.g., "In progress")
  4. Verify changes by viewing the issue after updates

Error Handling

  • Confirm issue exists: jira issue view <key>
  • Check authentication: jira me
  • Use --debug flag for troubleshooting

Recommended Agent Skills

Expand your agent's capabilities with these related and highly-rated skills.

l-lin/dotfiles

napkin

Maintain a per-repo napkin as a continuously curated runbook (not a session log). Activates EVERY session. Read and curate it before work, keep only recurring high-value guidance, organize by priority-sorted categories, and cap each category at top 10 items..

16 2
Explore
l-lin/dotfiles

datadog-pup

Use when interacting with Datadog resources using the `pup` CLI, especially for APM traces, metrics, monitors, notebooks, and synthetic tests.

16 2
Explore
l-lin/dotfiles

tmux

Use when you need a persistent terminal environment for long-running processes, programs requiring a TTY, REPLs, debuggers, TUI apps, or concurrent terminals — while the agent continues executing other commands.

16 2
Explore
l-lin/dotfiles

writing-skill

Use when creating new skills, editing existing skills, or verifying skills work before deployment

16 2
Explore
l-lin/dotfiles

clarifying-intent

Use when user asks to create, build, design, add, or generate something — especially when the request is vague, underspecified, or the scope is unclear. Use before starting creative work, features, components, or any new functionality.

16 2
Explore
l-lin/dotfiles

code-simplifier

Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Use when asked to "simplify code", "clean up code", "refactor for clarity", "improve readability", or review recently modified code for elegance. Focuses on project-specific best practices.

16 2
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results