Continue debugging a Linear issue systematically
Continues systematic debugging of Linear issues using scientific method and advanced tools.
/plugin marketplace add greyhaven-ai/claude-code-config/plugin install linear@grey-haven-pluginsissue ID or bug descriptionContinue debugging Linear issue: $ARGUMENTS
<ultrathink> Resume systematic debugging. Use scientific method. Leverage all available tools. Find root cause, not symptoms. </ultrathink> <megaexpertise type="advanced-debugging-specialist"> The assistant should combine systematic thinking, deep analysis, and comprehensive tooling to extract maximum understanding from the bug. </megaexpertise> <context> Continuing debugging for: $ARGUMENTS Need to understand bug state, leverage advanced tools, and find root cause </context> <requirements> - Find Linear issue and understand bug context - Use systematic thinking for hypothesis generation - Leverage deepwiki for library/framework understanding - Apply scientific debugging methodology - Document findings thoroughly </requirements> <actions> 1. Find Linear issue and bug context: - Extract issue ID from branch: git rev-parse --abbrev-ref HEAD - Get full issue details: mcp_linear.get_issue(id) - Review comments for reproduction steps and symptoms - Check linked PRs for previous fix attemptsUse mcp__sequential-thinking__sequentialthinking for systematic analysis:
Leverage mcp__deepwiki for deep understanding:
Apply scientific debugging:
logger.debug(f"[BUG-{issue_id}] State before: {state}, Inputs: {inputs}, Stack: {inspect.stack()[1].function}")
Advanced debugging techniques:
Root cause analysis:
Document and fix:
Write failing test that reproduces the bug
Implement minimal fix addressing root cause
Add defensive coding to prevent recurrence
Commit with Linear magic words (use actual team ID like ENG, DES, CVIREC):
Update Linear with detailed findings:
mcp__linear__create_comment(issueId, body="""
## Root Cause Analysis
- Hypothesis tested: ...
- Root cause: ...
- Why it happened: ...
- Fix approach: ...
""")
Knowledge capture:
.claude/debugging/[bug-pattern].md with learningsDebugging is detective work. The assistant should use all tools available - systematic thinking for hypotheses, deepwiki for understanding, and scientific method for proof.
Take a deep breath in, count 1... 2... 3... and breathe out. The assistant is now centered and should not hold back but give it their all.