mirror of
https://github.com/boshu2/agentops.git
synced 2026-09-14 15:08:13 +08:00
Boden Fuller
2b338ee0c3
Go fixes: - Fix UTF-8 boundary slicing in narrative truncation (rune-safe truncateRunes helper) - Add signal.Stop to rpi_serve signal handlers (prevent goroutine leak) - Replace CORS wildcard with localhost-only validation (prevent cross-site reads) - Surface SSE polling errors to client instead of silent continue - Extract section name constants (HISTORY/INTEL/TASK) from magic strings - Add intel_scope enum validation (none/topic/full) - Sort resolveSkillPath glob matches for deterministic resolution - Add random suffix to adhoc context IDs (prevent 1-second collision) - Surface writePromptAuditTrail errors to stderr unconditionally - Document RPI_RUN_ID env var in ao inject --help Doc fixes: - Replace stale /learn skill references with /retro --quick across 9 workflow docs - Replace .agents/retros/ with .agents/council/ in post-mortem SKILL.md + references - Reorder GOALS.md directives to sequential 1-8 numbering - Rename post-mortem Phase 2 steps from 4.x to EX.x - Update SKILL-TIERS.md: council + retro → council + knowledge lifecycle - Sync all changes to skills-codex mirror Epic: na-7r3 (6 issues, 2 waves)
2.6 KiB
2.6 KiB
name, description, estimated_time, phases
| name | description | estimated_time | phases |
|---|---|---|---|
| debug-cycle | Systematic debugging from symptoms to root cause to fix | 1-3 hours | 4 |
Debug Cycle Workflow
Purpose: Systematic investigation and resolution of bugs or issues
When to use:
- Production incidents (unknown root cause)
- Intermittent failures (hard to reproduce)
- Performance degradation (needs profiling)
- Integration issues (multiple components)
Token budget: 60-120k tokens across 1-3 sessions
Workflow Phases
Phase 1: Isolate (10-20% context)
↓
Phase 2: Locate (15-25% context)
↓
Phase 3: Fix (15-25% context)
↓
Phase 4: Verify & Learn (10-15% context)
Phase 1: Isolate
Goal: Reproduce the issue and isolate the component
Commands:
Read CLAUDE.md
/research "isolate [symptom]"
Activities:
- Reproduce the issue
- Identify affected components
- Gather logs, metrics, traces
- Narrow down scope
Output: Isolation report (which component/function)
Phase 2: Locate
Goal: Find exact root cause
Commands:
/research "locate root cause in [component]"
# Use history-explorer agent for git blame, past fixes
Activities:
- Read relevant code
- Trace execution path
- Check git history for related changes
- Identify the exact bug location
Output: Root cause identification (file:line)
Phase 3: Fix
Goal: Implement fix
Commands:
/plan [issue]-root-cause
/implement [issue]-plan
Activities:
- Design fix (may be simple or complex)
- Implement fix
- Add tests to prevent regression
- Validate fix resolves issue
Output: Working fix + regression test
Phase 4: Verify & Learn
Goal: Ensure fix works and extract learning
Commands:
/vibe recent
/retro --quick [issue]-fix
Activities:
- Full validation
- Deploy to staging/production
- Monitor for recurrence
- Extract debugging pattern
Output: Validated fix + debugging pattern
Example: Debug Auth Failures
# Phase 1: Isolate
Read CLAUDE.md
/research "isolate intermittent auth failures"
# Finding: Failures at 5pm daily, connection timeouts
# Component: Redis connection pool
# Phase 2: Locate
/research "locate root cause in Redis pool"
# Root cause: config/redis.yaml:15 - pool_size: 10 (too small)
# Phase 3: Fix
/plan redis-pool-fix
/implement redis-pool-fix
# Fix: Increase pool size to 100, add health checks
# Phase 4: Verify
/vibe recent
# ✅ Load test: No failures at 3x traffic
/retro --quick redis-pool-debugging
# Pattern: Intermittent failures + time correlation = resource exhaustion
Start debug cycle with: Read CLAUDE.md → describe symptoms