Skip to content

chore: enhance root cause analysis for /create-bug skill#26722

Merged
chrisleewilcox merged 1 commit into
mainfrom
MMQA-1523-update-create-bug-root-cause-analysis
Feb 28, 2026
Merged

chore: enhance root cause analysis for /create-bug skill#26722
chrisleewilcox merged 1 commit into
mainfrom
MMQA-1523-update-create-bug-root-cause-analysis

Conversation

@chrisleewilcox

@chrisleewilcox chrisleewilcox commented Feb 28, 2026

Copy link
Copy Markdown
Contributor

Description

Updates the /create-bug Claude Code skill command to include a full root cause analysis workflow (Step 6) with three phases:

  • 6a: Investigate root cause — trace through the code to identify exact files, lines, and logic
  • 6b: Identify regression PRs — check git history against previous releases
  • 6c: Scope analysis — search for same pattern across codebase, file separate bugs for other affected features

Also updates the comment format to include all required sections.

Changelog

CHANGELOG entry: null

Related issues

Fixes:

MMQA-1523

Manual testing steps

Feature: Create Bug Skill Root Cause Analysis

  Scenario: user runs /create-bug and opts into root cause investigation
    Given user has Claude Code open in the metamask-mobile repo

    When user runs /create-bug and files a bug report
    And user opts into root cause investigation
    Then Claude performs root cause investigation (6a)
    And Claude identifies regression PRs by comparing release branches (6b)
    And Claude performs scope analysis to find same pattern elsewhere (6c)
    And Claude posts a comment with summary, regression PRs, error flow, scope of impact, key files, suggested fix, and related bug links

Screenshots/Recordings

Before

N/A

After

Run /create-bug in Claude Code terminal and opt into root cause investigation to see the full 3-phase workflow.

Pre-merge author checklist

Pre-merge reviewer checklist

  • I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
  • I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

Add Step 6 to the create-bug command with three phases:
- 6a: Investigate root cause (trace through code)
- 6b: Identify regression PRs (git history comparison)
- 6c: Scope analysis (search for same pattern, file separate bugs)

Also updates the comment format to include regression PRs, full scope
of impact, and links to related bugs.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

@metamaskbot metamaskbot added the team-qa QA team label Feb 28, 2026
@github-actions

Copy link
Copy Markdown
Contributor

🔍 Smart E2E Test Selection

  • Selected E2E tags: None (no tests recommended)
  • Selected Performance tags: None (no tests recommended)
  • Risk Level: low
  • AI Confidence: 98%
click to see 🤖 AI reasoning details

E2E Test Selection:
The only changed file is .claude/commands/create-bug.md, which is a Claude AI command configuration file. This file contains instructions for how Claude should handle bug creation workflows - specifically adding more detailed root cause analysis steps (investigating regression PRs, scope analysis, and enhanced comment formatting). This is purely documentation/configuration for AI tooling and has absolutely no impact on:

  1. Application source code
  2. E2E test infrastructure or test files
  3. Build configuration
  4. CI/CD workflows
  5. Any user-facing functionality

No E2E tests are needed as this change cannot affect any application behavior or test execution.

Performance Test Selection:
This change only modifies a Claude AI command configuration file (.claude/commands/create-bug.md) which is documentation for AI tooling. It has no impact on application code, UI rendering, data loading, or any performance-sensitive areas of the app. No performance tests are needed.

View GitHub Actions results

@chrisleewilcox chrisleewilcox added the needs-dev-review PR needs reviews from other engineers (in order to receive required approvals) label Feb 28, 2026
@github-project-automation github-project-automation Bot moved this to Needs dev review in PR review queue Feb 28, 2026
@chrisleewilcox chrisleewilcox added No QA Needed Apply this label when your PR does not need any QA effort. no-changelog no-changelog Indicates no external facing user changes, therefore no changelog documentation needed labels Feb 28, 2026
@chrisleewilcox chrisleewilcox changed the title chore: update /create-bug skill with full root cause analysis workflow chore: enhance root cause analysis for /create-bug skill Feb 28, 2026
@github-project-automation github-project-automation Bot moved this from Needs dev review to Review finalised - Ready to be merged in PR review queue Feb 28, 2026
@chrisleewilcox chrisleewilcox added this pull request to the merge queue Feb 28, 2026
Merged via the queue into main with commit 8a48496 Feb 28, 2026
103 of 108 checks passed
@chrisleewilcox chrisleewilcox deleted the MMQA-1523-update-create-bug-root-cause-analysis branch February 28, 2026 01:13
@github-actions github-actions Bot locked and limited conversation to collaborators Feb 28, 2026
@github-actions github-actions Bot removed the needs-dev-review PR needs reviews from other engineers (in order to receive required approvals) label Feb 28, 2026
@metamaskbot metamaskbot added the release-7.69.0 Issue or pull request that will be included in release 7.69.0 label Feb 28, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

No QA Needed Apply this label when your PR does not need any QA effort. no-changelog no-changelog Indicates no external facing user changes, therefore no changelog documentation needed release-7.69.0 Issue or pull request that will be included in release 7.69.0 size-S team-qa QA team

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

3 participants