jira

Manage Jira issue transitions and link pull requests via REST API.

1|Updated Jul 1, 2026
One-click install
npx skills add https://github.com/marcuskrogh/skills --skill jira-marcuskrogh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jira
Source: https://github.com/marcuskrogh/skills/tree/main/skills/jira
Command: npx skills add https://github.com/marcuskrogh/skills --skill jira-marcuskrogh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill automates the synchronization of development workflows with Jira, eliminating the manual overhead of updating ticket statuses, linking pull requests, and managing issue transitions.

Core Features & Use Cases

  • Automated Lifecycle Management: Seamlessly transition Jira tickets through states like In Progress, In Review, and Done based on your development activity.
  • Integrated Documentation: Automatically link pull requests and artifacts to Jira issues to maintain a clear audit trail.
  • Use Case: When you start implementing a feature, the skill automatically moves the corresponding Jira ticket to In Progress and attaches your technical design document for team visibility.

Quick Start

Ask the agent to update the status of the current Jira ticket to In Review after you have pushed your latest code changes.

Frequently Asked Questions about jira

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Jira issue status transitions based on development activity?

Automate Jira issue status transitions by integrating the Jira REST API into your workflow to move tickets through states like In Progress, In Review, and Done based on development activity. This requires valid Atlassian API credentials and project-specific configuration to execute RESTful interactions.

Can I automatically link pull requests to Jira issues?

Linking pull requests to Jira issues is supported through automated REST API operations that attach pull requests and project artifacts to their corresponding issues. This maintains a clear audit trail and integrated documentation within your Jira projects.

Do I need Atlassian API credentials to manage Jira tickets through workflow automation?

Valid Atlassian API credentials are required to execute RESTful interactions for Jira issue lifecycle management. You also need project-specific configuration to authenticate and manage issue tracking, ticket updates, and status transitions.

What's the best way to update Jira ticket statuses after pushing code changes?

The best way to update Jira ticket statuses after pushing code is to use workflow automation that triggers REST API operations to transition issues. You can ask your agent to update the status of the current Jira ticket to In Review after pushing your latest code changes.

Why does manual Jira issue management slow down development workflows?

Manual Jira issue management slows down workflows because it creates overhead from manually updating ticket statuses, linking pull requests, and managing issue transitions. Automating this synchronization with the REST API eliminates the manual overhead of tracking development activity.

Does this Jira REST API integration support attaching technical design documents to tickets?

Attaching technical design documents to Jira tickets is supported as part of integrated documentation features. When you start implementing a feature, the skill can move the corresponding Jira ticket to In Progress and attach your technical design document for team visibility.