manage-issue-analyze

Analyze codebase issues and append root-cause records to issues.jsonl.

511|63|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/catlog22/Maestro-Flow --skill manage-issue-analyze
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: manage-issue-analyze
Source: https://github.com/catlog22/Maestro-Flow/tree/main/.codex/skills/manage-issue-analyze
Command: npx skills add https://github.com/catlog22/Maestro-Flow --skill manage-issue-analyze

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates root-cause analysis for a specific issue by gathering relevant codebase context, running a delegated CLI analysis, and attaching a structured analysis record to the repository's issues.jsonl so engineers can quickly understand cause and scope.

Core Features & Use Cases

  • Context Gathering: Greps repository files for keywords from the issue or spawns a semantic explore agent to produce file:line evidence and relevance snippets.
  • Delegated CLI Analysis: Builds a safe prompt (written to a temp file) and invokes maestro delegate to run a structured analysis in analysis mode with a chosen tool (gemini or qwen).
  • Append-only Issue Recording: Validates the issue, parses and updates .workflow/issues/issues.jsonl with an analysis object and appended issue_history entry; preserves all other fields.
  • Use Case: Triage an open bug report by collecting related code locations, running an LLM-led analysis, and recording a verifiable, evidence-backed root-cause for downstream planning and fixes.

Quick Start

Run manage-issue-analyze with the target issue ID to gather context, run CLI analysis, and append a structured analysis to .workflow/issues/issues.jsonl.

Frequently Asked Questions about manage-issue-analyze

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

FAQPage Schema
How do I automate root-cause analysis for a bug in my codebase?

To automate root-cause analysis, this Skill gathers codebase context via keyword grep or a semantic explore agent, delegates structured CLI analysis using gemini or qwen, and appends an evidence-backed record to .workflow/issues/issues.jsonl.

How does an issues.jsonl file work with automated issue analysis?

The issues.jsonl file stores structured analysis records. The Skill parses and updates this file by appending an analysis object and issue_history entry while preserving all other existing fields.

Can I delegate codebase issue analysis to an LLM through the CLI?

Yes, you can delegate issue analysis by writing a safe prompt to a temp file and invoking maestro delegate --mode analysis with a chosen tool like gemini or qwen to process the codebase context.

What is the best way to capture file:line evidence during issue triage?

Capturing file:line evidence is best done by greping repository files for issue keywords or spawning a semantic explore agent, which produces relevance snippets for the analysis record.

Do I need a specific CLI tool to run structured issue analysis?

You need the maestro CLI to run structured analysis, as the workflow requires invoking maestro delegate to process prompts and generate the root-cause analysis output.

Why does my automated issue analysis require writing prompts to a temp file?

Writing prompts to a temp file ensures safe prompt construction before invoking the maestro delegate command, preventing injection issues and ensuring the CLI analysis processes the context correctly.