@devobsessed/code-captain 0.0.6 → 0.0.9

package/cursor/commands/status.md

@@ -1,4 +1,4 @@
-# Code Captain Status Command (cc: status)
+# Code Captain Status Command (status)
 
 ## Overview
 A command that provides developers with a comprehensive status report when starting work or switching context. Analyzes current git state, active work, and project health to orient developers and suggest next actions.
@@ -6,7 +6,7 @@ A command that provides developers with a comprehensive status report when start
 ## Command Structure
 
 ```bash
-cc: status
+/status
 ```
 
 Simple, no parameters needed. Works in any git repository with optional Code Captain project structure.
@@ -52,10 +52,10 @@ Simple, no parameters needed. Works in any git repository with optional Code Cap
 
 ### 4. Contextual Command Suggestions
 **Based on Current State:**
-- If mid-task: Suggest `cc: execute-task`
-- If no active work: Suggest `cc: create-spec`
-- If specifications exist: Suggest `cc: create-github-issues`
-- Always suggest `cc: swab` for code cleanup
+- If mid-task: Suggest `/execute-task`
+- If no active work: Suggest `/create-spec`
+- If specifications exist: Suggest implementation with `/execute-task`
+- Always suggest `/swab` for code cleanup
 
 ## Output Format
 
@@ -84,10 +84,10 @@ Simple, no parameters needed. Works in any git repository with optional Code Cap
    • Review recent main branch changes (3 new commits)
 
 ⚡ QUICK COMMANDS
-   cc: execute-task     # Continue current task
-   cc: commit-wip       # Commit work in progress  
-   cc: sync-main        # Pull latest from main
-   cc: swab             # Quick code cleanup
+   /execute-task     # Continue current task
+   /commit-wip       # Commit work in progress  
+   /sync-main        # Pull latest from main
+   /swab             # Quick code cleanup
 
 ### Clean State Example
 
@@ -109,9 +109,9 @@ Simple, no parameters needed. Works in any git repository with optional Code Cap
    • Perform maintenance tasks
 
 ⚡ QUICK COMMANDS
-   cc: create-spec      # Plan new feature
-   cc: swab             # Clean up existing code
-   cc: review-specs     # Check previous specifications
+   /create-spec      # Plan new feature
+   /swab             # Clean up existing code
+   /review-specs     # Check previous specifications
 
 ### Problem State Example
 
@@ -142,8 +142,8 @@ Simple, no parameters needed. Works in any git repository with optional Code Cap
    • Continue or restart task 1.4
 
 ⚡ QUICK COMMANDS
-  cc: execute-task     # Continue current task
-  cc: swab            # Code cleanup
+  /execute-task     # Continue current task
+  /swab            # Code cleanup
 
 ## Implementation Details
 
@@ -282,7 +282,7 @@ pip check
 ### Morning Routine
 ```bash
 # Developer starts their day
-$ cc: status
+$ /status
 
 # Gets oriented on yesterday's work
 # Sees exactly what to do next
@@ -292,7 +292,7 @@ $ cc: status
 ### Context Switching
 ```bash
 # After meetings, interruptions, or breaks
-$ cc: status
+$ /status
 
 # Quick reminder of current state
 # Understand what changed while away
@@ -302,7 +302,7 @@ $ cc: status
 ### Project Handoff
 ```bash
 # When picking up someone else's work
-$ cc: status
+$ /status
 
 # Understand current project state
 # See what was being worked on
@@ -336,8 +336,8 @@ $ cc: status
    • Create first feature specification
 
 ⚡ QUICK COMMANDS
-   cc: init             # Initialize Code Captain
-   cc: create-spec      # Create first specification
+   /init             # Initialize Code Captain
+   /create-spec      # Create first specification
 ```
 
 ### Corrupted Project State
@@ -353,8 +353,8 @@ $ cc: status
    • Check build configuration
 
 ⚡ RECOVERY COMMANDS
-   cc: doctor           # Diagnose and fix common issues
-   cc: reset-deps       # Reinstall dependencies
+   /doctor           # Diagnose and fix common issues
+   /reset-deps       # Reinstall dependencies
 ```
 
 ## Security & Privacy
@@ -410,4 +410,15 @@ $ cc: status
 
 ---
 
-*⚓ Keep your bearings, maintain your heading, and always know where you stand in the code.*
+*⚓ Keep your bearings, maintain your heading, and always know where you stand in the code.*
+
+## Suggested Next Actions
+
+Based on project state analysis, suggest relevant next steps:
+
+- **No specs**: Suggest `/create-spec` or `/plan-product`
+- **Specs ready for implementation**: Suggest `/execute-task`
+- **Tasks ready**: Suggest `/execute-task`
+- **Code quality issues**: Suggest `/swab`
+- **Missing architecture**: Suggest `/create-adr`
+- **Research needed**: Suggest `/research`

package/cursor/commands/swab.md

@@ -1,18 +1,21 @@
-# Code Captain Swab Command (cc: swab)
+# Code Captain Swab Command (swab)
 
 ## Overview
 
 A deck-cleaning agent that makes one small, focused improvement to the codebase, following the "Boy Scout Rule" - leave the code cleaner than you found it. This command identifies the single best small cleanup opportunity and applies it with your approval.
 
-## Usage
+## Command Process
 
-```bash
-cc: swab
-```
+### Step 0: Initialize Progress Tracking
 
-**Note:** No options, no flags, no complexity. Just simple deck cleaning.
+**Create todos for the swab process using `todo_write`:**
 
-## Command Process
+```
+- Scan codebase for improvement opportunities [in_progress]
+- Prioritize and select best cleanup option [pending]
+- Present cleanup suggestion to user [pending]
+- Apply approved change [pending]
+```
 
 ### Step 1: Codebase Scanning
 
@@ -34,6 +37,8 @@ cc: swab
 
 ### Step 2: Opportunity Prioritization
 
+**Update progress:** Mark "Scan codebase for improvement opportunities" as `[completed]` and "Prioritize and select best cleanup option" as `[in_progress]`
+
 **Selection Criteria:**
 1. **Clarity Impact** - How much clearer will the code be?
 2. **Risk Level** - How certain are we this won't break anything?
@@ -49,6 +54,8 @@ cc: swab
 
 ### Step 3: Present Single Best Option
 
+**Update progress:** Mark "Prioritize and select best cleanup option" as `[completed]` and "Present cleanup suggestion to user" as `[in_progress]`
+
 **Display Format:**
 ```
 🧽 Swabbing the deck... found some mess in {filename}
@@ -66,12 +73,16 @@ Clean this up? [y/N]
 
 ### Step 4: Apply Change
 
+**Update progress:** Mark "Present cleanup suggestion to user" as `[completed]` and "Apply approved change" as `[in_progress]`
+
 **If approved:**
-- Make the exact replacement using search/replace
+- Make the exact replacement using search and replace
 - Verify the change was applied correctly
+- Mark "Apply approved change" as `[completed]`
 - Show success message: "✅ Deck swabbed! One less mess aboard."
 
 **If declined:**
+- Mark "Apply approved change" as `[completed]` (no change needed)
 - Exit gracefully with: "🧽 Deck inspection complete. No changes made."
 
 ## Core Rules
@@ -95,7 +106,7 @@ RULES:
 - Prioritize clarity and safety over cleverness
 - Preserve all existing functionality exactly
 - Be extremely conservative - if ANY uncertainty, do nothing
-- Provide exact search/replace strings
+- Provide exact search and replace strings
 - Focus on high-impact, zero-risk improvements
 
 SCAN PRIORITIES:
@@ -187,6 +198,44 @@ This might happen if the file was modified since scanning.
 Try running the command again.
 ```
 
+## Example Todo Progression
+
+**Initial:**
+
+```
+- Scan codebase for improvement opportunities [in_progress]
+- Prioritize and select best cleanup option [pending]
+- Present cleanup suggestion to user [pending]
+- Apply approved change [pending]
+```
+
+**After scanning:**
+
+```
+- Scan codebase for improvement opportunities [completed]
+- Prioritize and select best cleanup option [in_progress]
+- Present cleanup suggestion to user [pending]
+- Apply approved change [pending]
+```
+
+**After prioritization:**
+
+```
+- Scan codebase for improvement opportunities [completed]
+- Prioritize and select best cleanup option [completed]
+- Present cleanup suggestion to user [in_progress]
+- Apply approved change [pending]
+```
+
+**Final:**
+
+```
+- Scan codebase for improvement opportunities [completed]
+- Prioritize and select best cleanup option [completed]
+- Present cleanup suggestion to user [completed]
+- Apply approved change [completed]
+```
+
 ## Integration Notes
 
 This command integrates with the existing Code Captain ecosystem by:
@@ -195,14 +244,16 @@ This command integrates with the existing Code Captain ecosystem by:
 2. **Leveraging existing tools** - Uses `codebase_search`, `read_file`, `search_replace`
 3. **Maintaining simplicity** - No complex configuration or state management
 4. **Respecting user control** - Always asks permission before making changes
+5. **Progress tracking** - Uses `todo_write` for visibility into command progress
+6. **Quality foundation** - Complements specification and implementation commands by maintaining code quality, supporting the overall project foundation alongside `.code-captain` documentation
 
 ## Future Enhancements
 
 Potential future improvements (not in initial version):
 
-- **Directory targeting**: `cc: swab src/components/`
-- **File type filtering**: `cc: swab --js-only`
-- **Batch mode**: `cc: swab --batch` (apply multiple small changes)
+- **Directory targeting**: `/swab src/components/`
+- **File type filtering**: `/swab --js-only`
+- **Batch mode**: `/swab --batch` (apply multiple small changes)
 - **Learning**: Remember which types of cleanups user prefers
 - **Metrics**: Track improvements made over time