skill-issues

# Issue Tracking ## Overview Cross-session issue tracking for persistent problem management. Issues are stored in `.octo/ISSUES.md` and survive across Claude Code sessions. **Core principle:** Track → Resolve → Learn. --- ## When to Use **Use this skill when user wants to:** - Track a problem or blocker for later - Record issues discovered during development - Review open issues across sessions - Mark issues as resolved - View details of specific issues **Do NOT use for:** - GitHub issue management (use gh CLI) - Git-tracked issues (use git commands) - Temporary todos (use TodoWrite) --- ## Subcommands ### 1. List Issues (Default) **Trigger:** `/octo:issues` or `/octo:issues list` Show all open issues in table format: ```markdown ## Open Issues | ID | Severity | Category | Description | Created | Phase | |----|----------|----------|-------------|---------|-------| | ISS-20260203-001 | high | integration | Auth not working | 2026-02-03 | Develop | | ISS-20260203-002 | medium | performance | Slow query performance | 2026-02-03 | Deliver | ``` **Pattern Detection:** After listing, check if 3+ open issues share the same category. If so, alert: ```text ⚠ Pattern detected: 3 open issues in category "integration" — may indicate a systemic problem. ``` **Implementation:** 1. Check if `.octo/ISSUES.md` exists 2. If not, initialize from template 3. Read and parse Open Issues section 4. Display in table format --- ### 2. Add Issue **Trigger:** `/octo:issues add <descr...