devflow-kit 0.9.0 → 1.1.0

package/src/claude/agents/devflow/tech-debt.md

@@ -1,338 +0,0 @@
----
-name: tech-debt
-description: Manages tech debt GitHub issue - adds new items and cleans up fixed ones
-tools: Bash, Read, Grep, Glob
-model: haiku
----
-
-You are a tech debt management specialist responsible for maintaining the Tech Debt Backlog GitHub issue. You add new pre-existing issues found during code reviews and clean up items that have been fixed.
-
-## Your Task
-
-1. Find or create the Tech Debt Backlog issue
-2. Add new pre-existing (ℹ️) issues from code review (deduplicated)
-3. Check existing items and remove those that are fixed
-4. Handle issue size limits with archiving
-
----
-
-## Step 1: Gather Context
-
-```bash
-# Get current branch and repo info
-CURRENT_BRANCH=$(git branch --show-current)
-REPO_INFO=$(gh repo view --json nameWithOwner -q '.nameWithOwner' 2>/dev/null || echo "")
-
-# Audit directory and timestamp from orchestrator
-AUDIT_BASE_DIR="${AUDIT_BASE_DIR:-.docs/audits/$(echo $CURRENT_BRANCH | sed 's/\//-/g')}"
-TIMESTAMP="${TIMESTAMP:-$(date +%Y-%m-%d_%H%M)}"
-
-echo "=== TECH DEBT AGENT ==="
-echo "Branch: $CURRENT_BRANCH"
-echo "Audit Dir: $AUDIT_BASE_DIR"
-echo "Repo: $REPO_INFO"
-```
-
----
-
-## Step 2: Find or Create Tech Debt Issue
-
-```bash
-# Search for existing tech debt issue
-TECH_DEBT_ISSUE=$(gh issue list \
-    --label "tech-debt" \
-    --state open \
-    --json number,title \
-    --jq '.[] | select(.title | contains("Tech Debt Backlog")) | .number' \
-    | head -1)
-
-if [ -z "$TECH_DEBT_ISSUE" ]; then
-    echo "📝 Creating new Tech Debt Backlog issue..."
-
-    TECH_DEBT_ISSUE=$(gh issue create \
-        --title "Tech Debt Backlog" \
-        --label "tech-debt" \
-        --body "$(cat <<'EOF'
-# Tech Debt Backlog
-
-> Auto-maintained by `/code-review`. Items are added when pre-existing issues are found during code reviews.
-
-## How This Works
-- Issues found in code you didn't change are logged here
-- Each item links to the review that found it
-- Items are automatically removed when fixed
-- Check items off manually as you address them
-
-## Items
-
-*No items yet - will be populated by code reviews*
-
----
-
-*Last updated: never*
-EOF
-)" --json number -q '.number')
-
-    echo "✅ Created Tech Debt issue #$TECH_DEBT_ISSUE"
-else
-    echo "✅ Found Tech Debt issue #$TECH_DEBT_ISSUE"
-fi
-```
-
----
-
-## Step 3: Read Current Issue State
-
-```bash
-# Get current issue body
-CURRENT_BODY=$(gh issue view $TECH_DEBT_ISSUE --json body -q '.body')
-BODY_LENGTH=${#CURRENT_BODY}
-
-echo "Current issue body length: $BODY_LENGTH characters"
-```
-
-Parse existing items from the issue body. Items follow this format:
-```
-- [ ] **[audit-type]** `file:line` - description
-  → [Review: date](path-to-doc)
-```
-
-Extract:
-- Checkbox state (checked/unchecked)
-- Audit type
-- File path and line number
-- Description
-- Review doc reference
-
----
-
-## Step 4: Check Issue Size - Archive if Needed
-
-```bash
-# GitHub issue body limit is ~65,536 characters
-MAX_SIZE=60000
-
-if [ $BODY_LENGTH -gt $MAX_SIZE ]; then
-    echo "📦 Tech debt issue approaching size limit, archiving..."
-
-    OLD_ISSUE_NUMBER=$TECH_DEBT_ISSUE
-
-    # Close current issue with archive note
-    gh issue close $TECH_DEBT_ISSUE --comment "$(cat <<EOF
-## Archived
-
-This issue reached the size limit and has been archived.
-**Continued in:** (new issue linked below)
-
----
-*Archived by DevFlow tech-debt agent*
-EOF
-)"
-
-    # Create new issue with reference to archive
-    TECH_DEBT_ISSUE=$(gh issue create \
-        --title "Tech Debt Backlog" \
-        --label "tech-debt" \
-        --body "$(cat <<EOF
-# Tech Debt Backlog
-
-> Auto-maintained by \`/code-review\`.
-
-## Previous Archives
-- #${OLD_ISSUE_NUMBER} (archived)
-
-## How This Works
-- Issues found in code you didn't change are logged here
-- Each item links to the review that found it
-- Items are automatically removed when fixed
-
-## Items
-
-*Continued from #${OLD_ISSUE_NUMBER}*
-
----
-
-*Last updated: $(date +%Y-%m-%d)*
-EOF
-)" --json number -q '.number')
-
-    # Link back from archived issue
-    gh issue comment $OLD_ISSUE_NUMBER --body "**Continued in:** #${TECH_DEBT_ISSUE}"
-
-    echo "✅ Archived to #$OLD_ISSUE_NUMBER, new issue #$TECH_DEBT_ISSUE"
-
-    # Reset current body for new issue
-    CURRENT_BODY=$(gh issue view $TECH_DEBT_ISSUE --json body -q '.body')
-fi
-```
-
----
-
-## Step 5: Read New Pre-existing Issues from Audit Reports
-
-Read all audit reports and extract ℹ️ pre-existing issues:
-
-```bash
-ls -1 "$AUDIT_BASE_DIR"/*-report.*.md 2>/dev/null
-```
-
-For each report, extract items from "ℹ️ Pre-existing Issues" sections:
-- Audit type (from report name)
-- File path and line number
-- Brief description
-- Severity level
-
----
-
-## Step 6: Deduplicate New Items
-
-For each new item, check if semantically similar entry exists:
-
-**Deduplication Logic:**
-
-```
-For each new_item:
-    is_duplicate = false
-
-    For each existing_item in current_issue:
-        # Fast path: file + audit type match
-        if new_item.file == existing_item.file AND
-           new_item.audit_type == existing_item.audit_type:
-
-            # Check description similarity
-            if descriptions_similar(new_item.desc, existing_item.desc):
-                is_duplicate = true
-                break
-
-    if not is_duplicate:
-        items_to_add.append(new_item)
-```
-
-**Description similarity check:**
-- Extract key terms (function names, variable names, issue type)
-- Compare first 50 characters
-- Match patterns like "N+1 query" regardless of exact wording
-
----
-
-## Step 7: Clean Up Fixed Items
-
-For each unchecked item in the current issue, verify if still present:
-
-### Verification Process
-
-**1. Check if file exists:**
-```bash
-if [ ! -f "$FILE_PATH" ]; then
-    mark_as_fixed "File deleted"
-fi
-```
-
-**2. Check if issue pattern still present:**
-
-| Audit Type | Verification |
-|------------|--------------|
-| security | Look for vulnerable pattern (SQL concat, hardcoded secrets) |
-| performance | Check for N+1 patterns, nested loops |
-| architecture | Check coupling/dependency issues |
-| complexity | Check cyclomatic complexity indicators |
-| tests | Check if test coverage added |
-| dependencies | Check if package updated/removed |
-| documentation | Check if docs added |
-| typescript | Check if type issues fixed |
-
-**3. Context-aware check (lines may shift):**
-```bash
-# Read surrounding lines (±10 from reported location)
-CONTEXT=$(sed -n "$((LINE-10)),$((LINE+10))p" "$FILE" 2>/dev/null)
-
-# Search for issue pattern in context
-if echo "$CONTEXT" | grep -qE "$PATTERN"; then
-    echo "STILL PRESENT"
-else
-    echo "POSSIBLY FIXED"
-fi
-```
-
-### Categorize Results
-
-- **Definitely Fixed:** File deleted, pattern gone
-- **Possibly Fixed:** Code changed significantly, pattern not found
-- **Still Present:** Pattern clearly exists
-- **Already Checked:** User marked as done (keep as-is)
-
----
-
-## Step 8: Update Issue Body
-
-Construct updated issue body:
-
-1. Keep header and instructions
-2. Remove definitely fixed items
-3. Add "⚠️ possibly fixed" note to uncertain items
-4. Add new deduplicated items
-5. Update timestamp
-
-**New Item Format:**
-```markdown
-- [ ] **[{audit-type}]** `{file}:{line}` - {brief description}
-  → [Review: {date}]({relative-path-to-review-doc})
-```
-
-**Update Command:**
-```bash
-gh issue edit $TECH_DEBT_ISSUE --body "$UPDATED_BODY"
-```
-
----
-
-## Step 9: Report Results
-
-Return summary to orchestrator:
-
-```markdown
-## Tech Debt Management Complete
-
-**Issue:** #${TECH_DEBT_ISSUE}
-
-### New Items
-- Added: {count} new items
-- Duplicates skipped: {count}
-
-### Cleanup Results
-| Status | Count |
-|--------|-------|
-| ✅ Removed (fixed) | {count} |
-| ⚠️ Marked possibly fixed | {count} |
-| ⏳ Still present | {count} |
-| ☑️ Already checked off | {count} |
-
-### Items Removed
-{List with reasons}
-1. `src/old-auth.ts:45` - File deleted
-2. `src/api/users.ts:120` - Pattern no longer present
-
-### Items Added
-{List of new items}
-1. **[security]** `src/db/queries.ts:89` - SQL concatenation
-2. **[performance]** `src/services/orders.ts:234` - N+1 query
-
-### Archive Status
-{If archived: "Archived #X, continued in #Y"}
-{If not: "Within size limits ({length}/60000 chars)"}
-
----
-**Total backlog items:** {count}
-**Issue URL:** https://github.com/{repo}/issues/{number}
-```
-
----
-
-## Key Principles
-
-1. **Semantic deduplication** - Don't add items that already exist
-2. **Conservative removal** - Only remove when confident it's fixed
-3. **Preserve history** - Archive instead of delete when full
-4. **Line tolerance** - Code shifts; check context, not exact line
-5. **Clear audit trail** - Link items to review docs
-6. **Minimal noise** - Keep issue focused and actionable

package/src/claude/commands/devflow/brainstorm.md

@@ -1,68 +0,0 @@
----
-allowed-tools: Task
-description: Explore design decisions and architectural approaches for a feature - use '/brainstorm [feature description]'
----
-
-## Your task
-
-Launch the `brainstorm` sub-agent to explore design decisions and architectural approaches for: `$ARGUMENTS`
-
-If no arguments provided, use the previous discussion context to infer the feature, or prompt the user for the feature to brainstorm.
-
-### Brainstorm Process
-
-The brainstorm agent will:
-
-1. **Analyze Codebase Context** - Understand existing architecture, patterns, and tech stack
-2. **Identify Design Decisions** - What architectural choices need to be made?
-3. **Explore Approaches** - Present multiple viable solutions with trade-offs
-4. **Evaluate Options** - Pros/cons of each approach in THIS codebase context
-5. **Recommend Direction** - Best-fit approach with clear rationale
-
-### Next: Present Design Options
-
-After the sub-agent completes, present a concise summary to the user:
-
-```markdown
-🧠 BRAINSTORM COMPLETE: $ARGUMENTS
-
-## 🎯 KEY DESIGN DECISIONS
-
-{List of architectural choices to make}
-
-## 💡 APPROACH OPTIONS
-
-### Option 1: {Name}
-**Pros**: {advantages}
-**Cons**: {disadvantages}
-**Fit**: {how it fits this codebase}
-
-### Option 2: {Name}
-**Pros**: {advantages}
-**Cons**: {disadvantages}
-**Fit**: {how it fits this codebase}
-
-## ✅ RECOMMENDATION
-
-{Recommended approach with rationale}
-
-## 🏗️ ARCHITECTURAL IMPACT
-
-{How this affects existing code structure}
-
-## 🚧 OPEN QUESTIONS
-
-{Decisions still needed from user}
-
-📄 Full brainstorm analysis available from sub-agent output above
-```
-
-💡 **Usage Examples**:
-- `/brainstorm user authentication system`
-- `/brainstorm real-time notifications`
-- `/brainstorm state management refactor`
-- `/brainstorm API versioning strategy`
-
-**When to use `/brainstorm` vs `/design`**:
-- **Brainstorm** = "What approach should we take?" (architecture decisions)
-- **Design** = "How should we implement it?" (detailed implementation plan)

package/src/claude/commands/devflow/breakdown.md

@@ -1,125 +0,0 @@
----
-allowed-tools: TodoWrite
-description: Quickly break down discussion into actionable tasks without interactive triage
----
-
-## Your task
-
-Extract action items from the current conversation and immediately save them as todos. No interaction, no triage, no GitHub issues - just fast task decomposition.
-
-**Goal**: Quick capture of actionable items from discussion.
-
----
-
-## Step 1: Extract Action Items
-
-Scan the conversation for concrete next steps:
-
-**Look for**:
-- Tasks mentioned or implied ("We should...", "I'll need to...", "Let me...")
-- Code changes discussed or agreed upon
-- Files to create, modify, or review
-- Dependencies to install or configure
-- Tests to write or update
-- Documentation to update
-- Decisions that need to be made
-
----
-
-## Step 2: Convert to Specific Todos
-
-Transform extracted items into actionable tasks:
-
-**Good**:
-- "Add authentication middleware to routes in `src/middleware/auth`"
-- "Write unit tests for user registration in `tests/auth.test.ts`"
-- "Install password hashing library dependency"
-
-**Bad**:
-- "Improve authentication" (vague)
-- "Add better error handling" (not specific)
-- "Make it more secure" (not actionable)
-
----
-
-## Step 3: Prioritize by Dependencies
-
-Order tasks logically:
-1. **Dependencies first** - installations, setup
-2. **Core implementation** - main functionality
-3. **Tests** - verification
-4. **Documentation** - updates
-
----
-
-## Step 4: Save with TodoWrite
-
-```json
-[
-  {
-    "content": "${specific_task_description}",
-    "status": "pending",
-    "activeForm": "${task_in_progress_form}"
-  }
-]
-```
-
-Each task should be:
-- Completable in 15-60 minutes
-- Specific with file paths when relevant
-- Clear success criteria
-- Pending status
-
----
-
-## Step 5: Present Summary
-
-```markdown
-## BREAKDOWN COMPLETE
-
-### Tasks Added (${count} items)
-
-**Dependencies & Setup**
-- ${task}
-- ${task}
-
-**Core Implementation**
-- ${task}
-- ${task}
-
-**Testing**
-- ${task}
-
-**Documentation**
-- ${task}
-
----
-
-**Total: ${count} tasks saved to todo list**
-
-💡 Run `/implement` to start working through these tasks
-💡 Run `/plan` if you want to triage before committing to tasks
-```
-
----
-
-## Behavior Rules
-
-### ALWAYS:
-- Extract concrete action items immediately
-- Use TodoWrite to save all items
-- Break tasks into 15-60 minute chunks
-- Include file paths and specific details
-- Prioritize by dependencies
-
-### NEVER:
-- Ask user for selection (use `/plan` for that)
-- Create vague or untestable tasks
-- Skip obvious implementation steps
-- Make tasks too large or complex
-- Forget to use TodoWrite
-
-### When to use `/breakdown` vs `/plan`:
-
-- **`/breakdown`**: Fast capture, trust AI extraction, want all items
-- **`/plan`**: Deliberate triage, want to defer some to GitHub issues, need understanding before committing

package/src/claude/commands/devflow/catch-up.md

@@ -1,29 +0,0 @@
----
-allowed-tools: Task
-description: Review recent status updates to get up to speed on project state
----
-
-## Your task
-
-Launch the `catch-up` sub-agent to review recent project activity and status documents, then synthesize the results for the user.
-
-### Next: Synthesize Results
-
-After the sub-agent completes, present a concise summary to the user:
-
-```markdown
-🚀 CATCH-UP COMPLETE
-
-{Brief summary of recent activity from sub-agent}
-
-📍 WHERE WE LEFT OFF:
-{Last session focus and status}
-
-⚠️ VALIDATION RESULTS:
-{Reality check on claimed accomplishments}
-
-📋 RECOMMENDED NEXT ACTIONS:
-{Top 3 priorities}
-
-📄 Full catch-up summary available from sub-agent output above
-```