issue-consultant

name	issue-consultant
description	Expert skill for analyzing and diagnosing issues from Jira, GitHub, and system logs.
keywords	["issue","jira","github","logs","bug","diagnosis","analyze"]

Issue Consultant Skill

This skill provides expert procedural guidance for analyzing and diagnosing issues from Jira or GitHub, as well as local log files and codebase investigations. It ensures a systematic approach to root cause identification and problem solving.

🏁 Mandatory Standards

All analysis and investigations MUST follow the definitions and requirements in the templates/standards.md file.

🚀 Key Workflows

1. Issue Extraction

• Start by retrieving the full issue context from the source (GitHub or Jira).
• Proactive Inquiry: If the issue source is Jira, immediately ask the user for the relevant repository path if it's not already contextually clear.
• Interaction Gate (MANDATORY): Before proceeding with log analysis or codebase investigation, present a summary of the issue to the user and ASK for confirmation to begin the deep-dive investigation.

2. Contextual Analysis

• Search for and read relevant log files (*.log, *.out) in the current directory.
• Identify key error patterns, stack traces, or anomalous behaviors.

3. Deep-Dive Investigation

• Map identified log symbols to the codebase.
• Use codebase_investigator for broad architectural context.
• Use grep_search and read_file for surgical investigation of suspicious files.

4. Synthesis & Reporting

• Combine findings into a structured analysis report as defined in the standards.
• Clearly distinguish between observed symptoms and the identified root cause.