michael-harris

DevTeam Issue Command

Development community intermediate

SOURCE https://github.com/michael-harris/devteam

Description

**Command:** `/devteam:issue <number>` Fix a GitHub issue by number. Automatically fetches details and implements a fix.

Installation

This entry records only its repository, not the path inside it, so there is no exact command to give. Open the source below and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

Repository README

This is the README for michael-harris/devteam, shared by 20 entries in this directory. It describes the repository, not this entry specifically.

DevTeam Issue Command

**Command:** `/devteam:issue `

Fix a GitHub issue by number. Automatically fetches details and implements a fix.

Usage

/devteam:issue 123             # Fix GitHub issue #123
/devteam:issue 456 --council   # Force Bug Council for complex diagnosis

Your Process

Phase 0: Initialize State Tracking

Before starting, initialize state in SQLite database (`.devteam/devteam.db`):

# Source the state management functions
source scripts/state.sh

# Initialize the database if needed
source scripts/db-init.sh

# Set project metadata
set_kv_state "metadata.created_at" "$(date -u +%Y-%m-%dT%H:%M:%SZ)"
set_kv_state "metadata.project_name" "Issue #123 Fix"
set_kv_state "metadata.project_type" "issue"

# Set issue details
set_kv_state "issue.number" "123"
set_kv_state "issue.title" "[from GitHub]"
set_kv_state "issue.type" "bug"           # bug | security | performance | enhancement
set_kv_state "issue.severity" "high"       # critical | high | medium | low
set_kv_state "issue.complexity" "moderate"  # simple | moderate | complex

# Set execution context
set_kv_state "current_execution.command" "/devteam:issue 123"
set_phase "diagnosis"

# Configure autonomous mode
set_kv_state "autonomous_mode.enabled" "true"
set_kv_state "autonomous_mode.max_iterations" "20"
set_kv_state "autonomous_mode.current_iteration" "0"
set_kv_state "autonomous_mode.circuit_breaker.consecutive_failures" "0"
set_kv_state "autonomous_mode.circuit_breaker.max_failures" "3"
set_kv_state "autonomous_mode.circuit_breaker.state" "closed"

Phase 1: Fetch Issue Details

# Fetch issue from GitHub
gh issue view 123 --json title,body,labels,comments,state

# Extract key information
- Title
- Description
- Steps to reproduce
- Labels (bug, enhancement, security, etc.)
- Comments (may have additional context)

Phase 2: Classify Issue

**Determine issue type:**

bug - Something broken
security - Security vulnerability
performance - Performance degradation
enhancement - Small feature request

**Determine severity:**

critical - System down, security vulnerability, data loss
high - Major functionality broken
medium - Important but workaround exists
low - Minor issue

**Determine complexity:**

simple - Clear cause, straightforward fix (1-2 files)
moderate - Requires investigation, multiple files
complex - Architectural issue, needs deep analysis

Phase 3: Bug Council (for complex bugs)

**Activate Bug Council if:**

Complexity is complex
Issue has no clear reproduction steps
Multiple failed fix attempts
--council flag specified

**Bug Council Process:**

// Spawn 5 diagnostic agents in parallel
const councilResults = await Promise.all([
  Task({
    subagent_type: "diagnosis:root-cause-analyst",
    model: "opus",
    prompt: `Analyze issue #${issueNumber}:
      Title: ${title}
      Description: ${body}

      Provide diagnosis with:
      - Ro