skills.rest
tomsoulage-dedalus
tomsoulage-dedalusCOMMUNITY
Explore all skills by this author →
GitHub

task-analyze

Analyze Jira tickets by fetching documents, investigating code, and generating fix hypotheses.

Updated May 18, 2026
Search Tags:#jira#codebase investigation#automated analysis#ticket analysis#fix hypothesis
One-click install
npx skills add https://github.com/tomsoulage-dedalus/presc-workflows-tools --skill task-analyze
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: task-analyze
Source: https://github.com/tomsoulage-dedalus/presc-workflows-tools/tree/main/skills/task-analyze
Command: npx skills add https://github.com/tomsoulage-dedalus/presc-workflows-tools --skill task-analyze

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires requests, python-dateutil, pyyaml, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill automates the analysis of Jira tickets, including fetching related documents, investigating the codebase, and proposing fix hypotheses, thereby streamlining the workflow and reducing manual effort.

Core Features & Use Cases

  • Jira Ticket Analysis: Automatically reads and analyzes Jira tickets.
  • Codebase Investigation: Searches the codebase for relevant information.
  • Fix Hypotheses Generation: Proposes fix hypotheses for defects or implementation hints for stories.
  • Documentation Generation: Saves a comprehensive analysis in an ANALYZE.md file.
  • Use Case: Use this Skill to quickly analyze a Jira ticket and generate a detailed analysis without creating any branches or pull requests.

Quick Start

Analyze the Jira ticket with key 'HORME-1234' using the task-analyze skill.

Frequently Asked Questions about task-analyze

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

FAQPage Schema
How do I automate Jira ticket analysis and codebase investigation?▼

Jira ticket analysis fetches related documents, investigates the codebase for relevant information, and generates fix hypotheses. This process outputs a comprehensive analysis saved in an ANALYZE.md file.

Can I generate fix hypotheses for Jira defects without creating branches?▼

Generating fix hypotheses analyzes Jira tickets and searches the codebase without creating branches or pull requests. It proposes fixes for defects or implementation hints for stories directly.

What do I need to set up before analyzing Jira tickets with this tool?▼

Analyzing Jira tickets requires Jira API access and environment variables configured for your domain, API token, and custom field. Python libraries requests, python-dateutil, and pyyaml are also required.

Does Jira ticket analysis work with stories as well as defects?▼

Jira ticket analysis works with both defects and stories. For defects, it proposes fix hypotheses, and for stories, it generates implementation hints. Both outputs are saved in an ANALYZE.md file.

What's the best way to document the results of automated Jira ticket analysis?▼

Documenting automated Jira ticket analysis results is handled automatically by saving a comprehensive analysis in an ANALYZE.md file. This file contains the fetched documents, codebase investigation, and fix hypotheses.

Related Skills

Explore More Software Engineering Skills→
klu-devklu-dev
2

jira-integration

Retrieve, analyze, update, and transition Jira tickets via Atlassian's API.

Community
Intermediate
ybsaybsa
3

gh-issues

Automate GitHub issue fixes by spawning parallel sub-agents to create branches and open pull requests.

Community
Advanced
Luney-IndustriesLuney-Industries
4

ship-task

Merge GitHub pull requests and transition Linear or Jira tickets to Done.

Official
Advanced
EricTechProEricTechPro
54

fix-ticket

Automate Jira bug fix workflows from ticket reading to QA verification.

Community
Advanced