shreypurohit/jira-dev-workflow-plugin

Create a Git branch from a Jira issue key with smart naming and repository safety checks. Use when the user asks to create or set up a branch for a ticket.

Post a free-text progress, note, or completion comment on a Jira issue. Use for prose updates the user dictates or asks you to compose — NOT for linking git branches/commits/PRs (use jira-link-work) and NOT for status changes (use jira-update-status).

Wrap up a finished Jira issue — post a confirmed completion comment AND transition it to the final Done status in one flow. Use only for final completion; for a bare status change use jira-update-status.

Link git branches, commits, or pull requests to a Jira issue by posting a comment built FROM git data (traceability between code and ticket). Use only when the content comes from git — for free-text prose comments use jira-comment.

Analyze Jira issue requirements and create structured implementation plans. Use when the user asks to plan, break down, or analyze what to build for a ticket.

Read, summarize, and search Jira issues through natural language. Use when looking up a ticket, extracting acceptance criteria, or listing issues with JQL.

Show current sprint status, your assigned tickets, and blockers at a glance. Use for sprint workload, board status, blockers, or standup prep — not for generic issue search.

Begin work on a Jira issue by transitioning it to In Progress. Use only for starting work; for any other status change use jira-update-status, and use jira-branch separately to create a Git branch.

Transition a Jira issue to an arbitrary status via dynamic discovery. Use for general status changes EXCEPT the two specialized cases — starting work (To Do → In Progress, use jira-start-work) and final completion (comment + done, use jira-complete).