jira-ticket-enrichment

Enrich Jira tickets with Sentry error analysis and a GitHub fix plan.

Updated Jan 18, 2026
One-click install
npx skills add https://github.com/rom-orlovich/agents-system --skill jira-ticket-enrichment
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jira-ticket-enrichment
Source: https://github.com/rom-orlovich/agents-system/tree/main/claude-code-cli/agents/planning-agent/skills/jira-enrichment
Command: npx skills add https://github.com/rom-orlovich/agents-system --skill jira-ticket-enrichment

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill orchestrates automatic enrichment of Jira tickets with Sentry error analysis and a GitHub fix plan that helps engineers move faster from incident to resolution.

Core Features & Use Cases

  • Sentry-to-Jira enrichment: Fetch complete error details and attach a rich context to the Jira ticket.
  • Code discovery & analysis: Locate relevant repository files and identify the likely root cause.
  • Plan generation & PR drafting: Create a comprehensive fix plan (PLAN.md) and draft a GitHub PR description for review.
  • Status updates: Update Jira with progress, comments, and links to the PR draft.

Quick Start

Trigger the jira-ticket-enrichment skill when a Jira issue is created from a Sentry error to fetch error details, locate affected code, generate a fix plan, and update Jira with a draft PR.

Frequently Asked Questions about jira-ticket-enrichment

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

FAQPage Schema
How do I automatically enrich a Jira ticket with Sentry error details?

You need MCP integrations configured for Sentry, GitHub, and Jira APIs. These connections allow the system to read error details, locate affected code in your repositories, and post updates and PR drafts directly back to Jira and GitHub.

Can I generate a GitHub pull request draft from a Sentry error automatically?

The process locates relevant repository files based on the Sentry error stack trace and generates a comprehensive fix plan. It then updates the original Jira ticket with comments, progress status, and a direct link to the drafted PR for review.

Do I need MCP integrations to connect Sentry, GitHub, and Jira?

The skill is triggered when a Jira issue is created from a Sentry error. It automatically reads the error context, discovers the relevant GitHub code, generates a fix plan, and updates Jira with progress and PR links.

What is the best way to move from a Sentry incident to a GitHub fix plan?

It automates code discovery and analysis by matching Sentry error details against your GitHub repositories. This identifies the likely root cause and generates a comprehensive fix plan without requiring manual codebase searching.

How does code discovery and root cause analysis work for Sentry errors?

After creating a Jira ticket from a Sentry error, the workflow automatically reads the error details, locates the relevant code in GitHub, generates a fix plan, and updates Jira with a draft PR for review.