analyze-gitlab

Analyze GitLab Issue Command

Purpose

Investigate a GitLab issue reporting a production problem by fetching issue details, extracting error information, searching the codebase for related code, analyzing git history, and generating a root cause analysis report.

Instructions for Claude

When this command is invoked, perform comprehensive root cause analysis for a GitLab issue:

Step 1: Gather Issue Information

If user provided issue IID (internal ID):

1. Read settings from .claude/thufir.local.md to get default project
2. Use gitlab MCP tool to fetch issue details:
   • Tool: gitlab_get_issue
   • Parameters: {issue_iid: <iid>}

If user provided issue URL:

1. Parse URL to extract group, project, and issue IID
2. Use gitlab MCP tool with parsed values

If no argument provided:

1. Use AskUserQuestion to ask:
   • "What is the GitLab issue number (IID)?"
   • Or "What project? (leave blank for default from settings)"

Extract from issue:

• Issue IID and title
• Description
• Labels (look for "production", "incident", "priority::1", "bug")
• Created/updated timestamps
• Comments/notes (read for additional context)
• Assignees
• Related merge requests mentioned
• Milestones

Step 2: Parse Error Information

From issue description and comments, extract:

1. Error messages:

   • Stack traces
   • Error names (e.g., "ConnectionPoolExhausted")
   • Error codes (500, 503, timeout, etc.)

2. Reproduction details:

   • Steps to reproduce
   • Affected features or endpoints
   • User actions that trigger error

3. Impact information:

   • When error first occurred (timestamp)
   • How many users affected
   • Frequency (one-time, intermittent, constant)
   • Geographic or segment-specific

4. System context:

   • Service or component mentioned
   • Environment (production, staging)
   • Browser or client information

Parse patterns like:

• "Users are getting 500 errors..."
• "Error: ConnectionPoolExhausted at 14:32 UTC"
• "Stack trace: ..."
• "Approximately 15,000 users affected"