dx-ticket-analyze

Compile a structured developer reference of files and assets from Azure DevOps or Jira tickets.

6|3|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/easingthemes/dx-aem-flow --skill dx-ticket-analyze
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dx-ticket-analyze
Source: https://github.com/easingthemes/dx-aem-flow/tree/main/plugins/dx-core/skills/dx-ticket-analyze
Command: npx skills add https://github.com/easingthemes/dx-aem-flow --skill dx-ticket-analyze

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Research Azure DevOps/Jira tickets to identify all involved source files and assets, enabling faster context for developers.

Core Features & Use Cases

  • Enumerates related source files, assets, and references across repos from a ticket
  • Produces a structured developer reference with file paths and asset links to speed onboarding and debugging
  • Use Case: Given an ADO URL or Jira key, generate a complete inventory of touched code and assets

Quick Start

Provide an ADO URL or Jira issue key to generate a ticket-research draft and accompanying context

Frequently Asked Questions about dx-ticket-analyze

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

FAQPage Schema
How do I find all source files related to a Jira or Azure DevOps ticket?▼

To find source files for a ticket, you analyze an ADO URL or Jira issue key to generate a structured developer reference. This output inventories file paths, assets, and related links across the codebase to speed onboarding and debugging.

What is the best way to compile a codebase inventory from a Jira issue key?▼

Compiling a codebase inventory from a Jira issue key involves prioritizing local documentation searches before scanning repositories. This approach assembles a complete context of touched code and assets for downstream analysis.

Can I enumerate documentation and assets tied to an Azure DevOps URL?▼

Yes, you can enumerate documentation and assets tied to an Azure DevOps URL. The process identifies associated references and assembles a complete context listing files, assets, and related links across the codebase.

How does ticket analysis work for identifying touched code and assets?▼

Ticket analysis works by prioritizing local documentation searches before scanning repositories to identify touched code and assets. It compiles a structured developer reference listing files and links associated with the given ticket.

Do I need a specific repository setup to analyze source files for a ticket?▼

You need an ADO URL or Jira issue key to begin analyzing source files for a ticket. The process scans repositories and local documentation to assemble a complete context of touched code and assets for the given ticket.