Menu
Create, list, view, and manage Jira issues via REST API; triggers on 'jira', 'create ticket', 'list issues', 'change type'.
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
GitHub and Git workflow helpers, Issues and Projects v2 management via gh CLI; triggers on 'github', 'create issue', 'list issues', 'github project', 'project board', 'sync tasks', 'create pr', 'pr checks', 'retrigger tests', 'bump version', 'push'.
PR workflow operations: create PRs, check status, link PRs to issues, poll for comments, address feedback, watch PRs, save notes to memory. Triggers on 'pr create', 'pr checks', 'pr link', 'pr poll', 'pr address', 'pr comments', 'pr remember', 'watch pr', 'watching'.
Lisa - intelligent assistant for memory and tasks. Triggers on 'lisa', 'hey lisa', or addressing lisa directly.
Permanent memory using Lisa.
Create, load, or summarize tasks via Graphiti MCP; triggers on 'tasks', 'list tasks', 'add task', usable by any model (Claude, Gemini).
Capture each prompt into Graphiti memory (episodes) for this repo/user.
| name | jira |
| description | Create, list, view, and manage Jira issues via REST API; triggers on 'jira', 'create ticket', 'list issues', 'change type'. |
Model-neutral helper to interact with Jira via Atlassian REST API v3. Supports creating issues, listing, viewing, assigning, and transitioning.
Use when the user says: "create a jira ticket", "list jira issues", "jira create", "show jira issue", "assign ticket".
Reads from ~/.jira.d/:
config.yml - endpoint, user, authentication-methodapi-token - raw API token (no variable assignment)Example config.yml:
endpoint: https://yourcompany.atlassian.net
user: your.email@company.com
authentication-method: api-token
# Create Epic
lisa jira create --type epic --project PROJ --summary "Feature title" --description "Description text"
# Create Story
lisa jira create --type story --project PROJ --summary "Story title" --parent PROJ-123
# Create Sub-task
lisa jira create --type subtask --project PROJ --summary "Sub-task title" --parent PROJ-123
# Create with assignment
lisa jira create --type task --project PROJ --summary "Task" --assign me
# List by project
lisa jira list --project PROJ --limit 10
# List with JQL
lisa jira list --jql "assignee = currentUser() ORDER BY created DESC" --limit 5
# List my issues
lisa jira list --mine --limit 10
lisa jira view PROJ-123
# Assign to self
lisa jira assign PROJ-123 --to me
# Assign to user
lisa jira assign PROJ-123 --to "user@company.com"
# Move to In Progress
lisa jira transition PROJ-123 --to "In Progress"
# Move to Done
lisa jira transition PROJ-123 --to "Done"
# Move to Code Review
lisa jira transition PROJ-123 --to "Code Review"
# Change Epic to Story
lisa jira change-type PROJ-123 --to story
# Change to Task
lisa jira change-type PROJ-123 --to task
Valid types: epic, story, task, subtask, bug
When a Pull Request is created, transition all associated Jira tickets to "Code Review":
PROJ-123)view command)# Example: Transition epic and all subtasks to Code Review
lisa jira transition PROJ-123 --to "Code Review"
# For subtasks (if in "To Do", first move to "In Progress")
for ticket in PROJ-124 PROJ-125 PROJ-126; do
lisa jira transition "$ticket" --to "Code Review"
done
Note: If a ticket is in "To Do", you may need to transition through "In Progress" first:
lisa jira transition PROJ-123 --to "In Progress"
lisa jira transition PROJ-123 --to "Code Review"
See also: git skill for PR creation, CI triggers, and test retriggers.
{
"status": "ok",
"action": "create",
"issue": {
"key": "PROJ-123",
"url": "https://company.atlassian.net/browse/PROJ-123",
"summary": "Feature title",
"type": "Epic"
}
}
{
"status": "ok",
"action": "list",
"issues": [
{"key": "PROJ-123", "summary": "...", "status": "To Do", "assignee": "John Doe"}
],
"total": 10
}
{
"status": "ok",
"action": "view",
"issue": {
"key": "PROJ-123",
"summary": "...",
"description": "...",
"status": "To Do",
"assignee": "John Doe",
"reporter": "...",
"created": "2026-01-13T...",
"subtasks": [...]
}
}
{
"status": "ok",
"action": "change-type",
"issue": {
"key": "PROJ-123",
"url": "https://company.atlassian.net/browse/PROJ-123",
"previousType": "Epic",
"newType": "story"
}
}
{
"status": "error",
"error": "Authentication failed",
"details": "..."
}
Standard Jira issue types (IDs may vary by project):
epic (10000) - Parent for featuresstory (10001) - User storiestask (10002) - General taskssubtask (10003) - Sub-tasks linked to parentbug (10004) - Bug reportslisa CLI binary — no scripts to run directly.