Manage Jira issues and sprints via natural language with approval workflows.
npx skills add https://github.com/albertms22/agent-toolkit --skill jira-albertms22
Please help me install this Agent Skill. Skill: jira Source: https://github.com/albertms22/agent-toolkit/tree/main/skills/jira Command: npx skills add https://github.com/albertms22/agent-toolkit --skill jira-albertms22
Helps teams interact with Jira using natural language to view, create, and manage issues without memorizing commands or forms.
Tell Claude to show PROJ-123 details, and it will fetch the issue and propose updates for your approval.
High-intent search queries and answers about installing and using this skill.
Jira issue management through natural language lets you view, create, and update tickets by simply describing what you need. The Skill detects issue keys in conversation, fetches details first, and requires explicit approval before applying any create, update, or transition operations.
Sprint status tracking works across both jira CLI and Atlassian MCP backends. The Skill detects the appropriate backend automatically, fetching sprint and backlog insights through natural language queries without requiring manual CLI commands.
Yes, Jira workflow transitions require explicit user approval. The Skill enforces a safe fetch-before-change workflow, ensuring all create, update, and transition operations are reviewed and approved before any modifications are applied to your tickets.
The best way to view Jira ticket details is to mention an issue key like PROJ-123 in conversation. The Skill detects the referenced key, fetches issue details, and proposes relevant updates or sprint insights for your review using natural language.
Linking Jira issues with natural language commands involves referencing multiple issue keys in conversation. The Skill provides issue linking guidance, fetches referenced tickets, and proposes the link relationship for your explicit approval before creating the association.
A key limitation of Jira automation via the Atlassian MCP backend is that all write operations require explicit user approval. The Skill cannot autonomously create, update, or transition issues without confirmation, enforcing a safe fetch-before-change workflow across both backends.
al-stevConfigure Atlassian API credentials for Jira and Confluence access.
bradtaylorsfAutomatically transition Jira tickets and add comments based on development events.
sunholo-dataAutomates end-to-end AILANG release management including pre-release checks, version bumps, changelog updates, git tagging, CI/CD verification, and release broadcasting.
saajunaidCreate and manage Jira issues from natural language via REST API or MCP.
