@devobsessed/code-captain 0.0.6 → 0.0.9

package/cursor/integrations/github/sync.md

@@ -1,305 +0,0 @@
-# Enhanced GitHub Sync Command (cc: sync)
-
-## Overview
-
-Advanced bidirectional synchronization between Code Captain local specs and GitHub issues using partitioned cache for optimal performance. This replaces the basic `sync-github-issues` with comprehensive sync capabilities.
-
-## Usage
-
-```bash
-cc: sync [--full] [--my-work-only] [--spec spec-name]
-```
-
-**Examples:**
-
-```bash
-cc: sync                              # Default incremental sync
-cc: sync --full                       # Full refresh (slower)
-cc: sync --my-work-only               # Sync only my assigned tasks (fastest)
-cc: sync --spec user-dashboard        # Sync specific spec only
-```
-
-## Command Process
-
-### Step 1: Sync Preparation
-
-**Validate GitHub access and repository:**
-- Verify GitHub CLI authentication
-- Check repository permissions
-- Confirm issue access
-
-### Step 2: Determine Sync Strategy
-
-**Incremental Sync (Default):**
-- Only fetch issues updated since last sync
-- Update local spec documents as needed
-
-**Full Sync:**
-- Fetch all issues with essential fields
-- Update all relevant spec documents
-- Comprehensive but slower
-
-**My Work Only:**
-- Only sync issues assigned to current user
-- Fastest option for personal workflow
-
-**Spec-Specific:**
-- Sync only issues related to specific spec/milestone
-- Efficient for focused work
-
-### Step 3: GitHub Data Retrieval
-
-**Authentication & Rate Limit Check:**
-
-Check GitHub CLI authentication and rate limits (Code Captain will use platform-appropriate commands based on your shell from `state.json`):
-- Verify GitHub CLI authentication status
-- Check API rate limit remaining
-
-**Incremental Sync Query:**
-
-Get last sync timestamp and fetch updated issues (Code Captain will use platform-appropriate commands based on your shell from `state.json`):
-- Read last sync timestamp from `.code-captain/state/index.json`
-- Use `gh issue list` to fetch issues updated since last sync
-- Include fields: number, title, state, assignees, labels, milestone, updatedAt
-
-**Full Sync Query:**
-
-Fetch all issues with comprehensive data:
-```
-gh issue list --json number,title,state,assignees,labels,milestone,createdAt,updatedAt --state all --limit 1000
-```
-
-**My Assignments Query:**
-
-Fetch issues assigned to current user:
-```
-gh issue list --json number,title,state,labels,milestone,updatedAt --assignee @me --state all
-```
-
-### Step 4: Data Transformation & Partitioning
-
-**Transform GitHub Issues to Code Captain Format:**
-
-```typescript
-interface GitHubIssue {
-  number: number;
-  title: string;
-  state: 'OPEN' | 'CLOSED';
-  assignees: Array<{login: string, name?: string}>;
-  labels: Array<{name: string, color: string}>;
-  milestone?: {title: string};
-  createdAt: string;
-  updatedAt: string;
-}
-
-interface CodeCaptainTask {
-  platform_id: string;
-  task_id: string;
-  title: string;
-  status: 'open' | 'in_progress' | 'completed' | 'blocked';
-  assignee: string | null;
-  priority: 'urgent' | 'high' | 'medium' | 'low';
-  spec_folder: string;
-  created_date: string;
-  last_modified: string;
-}
-```
-
-**Priority Extraction from Labels:**
-```typescript
-function extractPriority(labels: Array<{name: string}>): string {
-  const labelNames = labels.map(l => l.name.toLowerCase());
-  
-  if (labelNames.some(name => ['urgent', 'critical', 'p0'].includes(name))) {
-    return 'urgent';
-  }
-  if (labelNames.some(name => ['high-priority', 'high', 'p1'].includes(name))) {
-    return 'high';
-  }
-  if (labelNames.some(name => ['low-priority', 'low', 'p3'].includes(name))) {
-    return 'low';
-  }
-  return 'medium'; // Default
-}
-```
-
-**Status Mapping:**
-```typescript
-function mapGitHubState(state: string, assignees: Array<any>): string {
-  if (state === 'CLOSED') return 'completed';
-  if (state === 'OPEN' && assignees.length > 0) return 'in_progress';
-  if (state === 'OPEN' && assignees.length === 0) return 'open';
-  return 'open';
-}
-```
-
-### Step 5: Update Cache Partitions
-
-**Update index.json:**
-```json
-{
-  "last_sync": "2024-01-15T14:30:00Z",
-  "sync_status": "current",
-  "platform": "github",
-  "repository": "company/main-app",
-  "gh_cli_version": "2.40.1",
-  
-  "summary": {
-    "total_issues": 89,
-    "open_issues": 34,
-    "my_assigned": 3,
-    "available_tasks": 12,
-    "high_priority_open": 5
-  },
-
-  "my_active_work": [
-    {
-      "issue_number": 124,
-      "title": "Create dashboard route and controller",
-      "spec": "user-dashboard",
-      "task_id": "1.2",
-      "priority": "high"
-    }
-  ],
-
-  "attention_needed": [
-    "5 high-priority issues unassigned",
-    "user-dashboard spec has 2 blocked tasks"
-  ],
-
-  "specs_status": {
-    "user-dashboard": {"total": 5, "completed": 2, "in_progress": 2, "available": 1},
-    "payment-system": {"total": 8, "completed": 1, "in_progress": 3, "available": 4}
-  }
-}
-```
-
-**Update local specification documents:**
-- Update issue status in relevant spec files
-- Sync assignee information
-- Update completion status
-- Maintain traceability between specs and GitHub issues
-
-### Step 6: Conflict Detection & Resolution
-
-**Detect sync conflicts:**
-```json
-{
-  "conflicts": [
-    {
-      "type": "assignment_conflict",
-      "issue_number": 124,
-      "local_assignee": "alice-dev",
-      "github_assignee": "bob-dev", 
-      "detected_at": "2024-01-15T14:30:00Z",
-      "resolution": "pending"
-    },
-    {
-      "type": "status_conflict",
-      "issue_number": 125,
-      "local_status": "completed",
-      "github_status": "OPEN",
-      "detected_at": "2024-01-15T14:25:00Z", 
-      "resolution": "accept_github"
-    }
-  ]
-}
-```
-
-**Handle conflicts:**
-- Assignment conflicts: GitHub wins (most recent assignment)
-- Status conflicts: GitHub wins (authoritative state)
-- Title/description conflicts: GitHub wins
-- Log all conflicts for review
-
-### Step 7: Update Local Spec Files
-
-**Update spec files with latest GitHub state:**
-- Update task status indicators
-- Update assignee information
-- Update issue links
-- Preserve original spec content structure
-
-### Step 8: Generate Sync Report
-
-**Create sync summary:**
-```markdown
-✅ GitHub Sync Complete
-
-📊 Summary:
-- Sync Type: Incremental
-- Issues Updated: 15
-- Cache Files Updated: 3
-- Conflicts Detected: 2 (auto-resolved)
-
-📁 Updated Files:
-- Local specification documents updated with issue status
-- GitHub issue mappings synchronized
-
-⚠️ Conflicts Resolved:
-- Issue #124: Assignment updated (alice-dev → bob-dev)
-- Issue #125: Status updated (completed → open)
-
-🕐 Last Sync: 2024-01-15T14:30:00Z
-🔄 Next Recommended Sync: 2024-01-15T15:30:00Z
-```
-
-## Tool Integration
-
-**GitHub CLI Commands:**
-- `gh issue list` for fetching issues
-- `gh auth status` for authentication check
-- `gh api rate_limit` for rate limit monitoring
-
-**Code Captain Tools:**
-- `todo_write` for progress tracking
-- `read_file` for cache file management
-- `write` for cache updates
-- `MultiEdit` for spec file updates
-- `grep_search` for finding issue references
-
-## Error Handling
-
-**GitHub API Issues:**
-- Handle authentication failures gracefully
-- Implement rate limit backoff
-- Provide partial sync on API errors
-
-**Cache Corruption:**
-- Validate cache file integrity
-- Rebuild corrupted partitions
-- Maintain backup of previous state
-
-**Network Issues:**
-- Graceful degradation when offline
-- Resume interrupted syncs
-- Clear error messaging
-
-## Performance Optimizations
-
-**Incremental Updates:**
-- Only sync changed issues
-- Update affected cache partitions only
-- Parallel cache file updates
-
-**Memory Management:**
-- Stream large issue lists
-- Partition data by concern
-- Lazy load cache files
-
-**API Efficiency:**
-- Batch GitHub API calls
-- Use appropriate pagination
-- Cache expensive queries
-
-## Integration with Existing Commands
-
-**Enhances create-github-issues:**
-- Automatically sync after issue creation
-- Update cache with new issue mappings
-- Maintain bidirectional traceability
-
-**Works with existing workflows:**
-- Maintains compatibility with current spec formats
-- Preserves existing GitHub integration
-- Extends functionality without breaking changes

package/windsurf/README.md

@@ -1,254 +0,0 @@
-# Code Captain for Windsurf
-
-> **Codeium's AI-powered development environment with custom workflow integration**
-
-Windsurf provides advanced AI capabilities with custom workflow integration, built-in context management, and intelligent code coordination.
-
-## 🚀 Installation
-
-### Automatic Installation (Recommended)
-
-```bash
-npx @devobsessed/code-captain
-```
-
-The installer will detect Windsurf and install to:
-- `.windsurf/` - Custom workflows and rules
-- `.code-captain/` - Complete workflow system
-
-### Manual Installation
-
-```bash
-# Clone or download the windsurf/ directory contents to .windsurf/
-cp -r windsurf/ .windsurf/
-cp -r .code-captain/ .
-```
-
-## 🎯 Workflow Integration
-
-Code Captain in Windsurf uses custom workflow files that integrate with Windsurf's AI system:
-
-### Available Workflows
-Located in `.windsurf/workflows/`:
-
-- **`initialize.md`** - Project setup and analysis
-- **`create-spec.md`** - Feature specification creation
-- **`create-adr.md`** - Architecture Decision Records
-- **`execute-task.md`** - Test-driven development
-- **`explain-code.md`** - Code explanation with diagrams
-- **`status.md`** - Project status analysis
-- **`edit-spec.md`** - Specification modification
-- **`new-command.md`** - Custom command creation
-
-### Workflow Rules
-Located in `.windsurf/rules/`:
-
-- **`cc.md`** - Core Code Captain rules and guidelines
-
-## 🛠️ Available Workflows
-
-### 📋 Project Setup & Analysis
-- **Initialize Project** - Comprehensive project analysis and documentation setup
-- **Product Planning** - Strategic product planning with roadmap generation
-- **Technical Research** - Systematic 4-phase research methodology
-- **Custom Commands** - Create domain-specific workflow extensions
-
-### 📝 Requirements & Planning
-- **Feature Specifications** - Detailed specs with technical implementation details
-- **Architecture Decisions** - ADRs with systematic research and alternatives analysis
-- **Code Explanations** - Visual diagrams with comprehensive technical analysis
-- **Specification Editing** - Contract-first approach to specification modifications
-
-### ⚙️ Implementation
-- **Test-Driven Development** - Systematic TDD workflow with progress tracking
-- **Project Status** - Comprehensive status analysis with actionable recommendations
-- **Code Cleanup** - Incremental improvements following the Boy Scout Rule
-
-## 🔄 Workflow Examples
-
-### Project Initialization
-
-1. **Open Windsurf** and navigate to your project
-2. **Reference the initialize workflow**: `.windsurf/workflows/initialize.md`
-3. **Follow the systematic process** for project analysis
-4. **Review generated documentation** in `.code-captain/docs/`
-
-### Feature Development
-
-1. **Research Phase**
-   - Use `.windsurf/workflows/create-adr.md` for architectural decisions
-   - Reference research methodology from workflows
-
-2. **Specification Phase**
-   - Follow `.windsurf/workflows/create-spec.md`
-   - Generate comprehensive feature specifications
-
-3. **Implementation Phase**
-   - Use `.windsurf/workflows/execute-task.md`
-   - Follow TDD methodology with progress tracking
-
-4. **Status Monitoring**
-   - Reference `.windsurf/workflows/status.md`
-   - Get comprehensive project health analysis
-
-### Code Understanding
-
-1. **Code Explanation**
-   - Use `.windsurf/workflows/explain-code.md`
-   - Generate visual diagrams and technical analysis
-
-2. **Incremental Improvements**
-   - Follow best practices from `.windsurf/rules/cc.md`
-   - Apply small, focused improvements
-
-## 📁 File Organization
-
-Windsurf integration creates this structure:
-
-```
-.windsurf/
-├── workflows/
-│   ├── initialize.md
-│   ├── create-spec.md
-│   ├── create-adr.md
-│   ├── execute-task.md
-│   ├── explain-code.md
-│   ├── status.md
-│   ├── edit-spec.md
-│   └── new-command.md
-└── rules/
-    └── cc.md
-
-.code-captain/
-├── commands/              # Reference documentation
-├── docs/                  # Generated documentation
-├── research/              # Technical research reports
-├── decision-records/      # Architecture Decision Records
-├── specs/                 # Feature specifications
-│   └── YYYY-MM-DD-feature/
-│       ├── spec.md
-│       ├── user-stories/
-│       └── tasks.md
-└── cc.md                 # Complete reference guide
-```
-
-## 🎯 Windsurf-Specific Features
-
-### Custom Workflow Integration
-- **Workflow-based execution** aligned with Windsurf's AI coordination
-- **Context-aware processing** using Windsurf's advanced context management
-- **Intelligent file organization** with automatic workspace awareness
-
-### Advanced AI Coordination
-- **Multi-step workflow execution** with AI guidance
-- **Context preservation** across workflow phases
-- **Intelligent tool selection** based on workflow requirements
-
-### Built-in Best Practices
-- **Critical thinking guidelines** from `windsurf/rules/cc.md`
-- **Systematic approaches** to complex development tasks
-- **Quality-focused workflows** with verification steps
-
-## 🚀 Advanced Usage
-
-### Custom Workflow Creation
-
-Create new workflows in `.windsurf/workflows/`:
-
-```markdown
-# Custom Workflow
-
-## Overview
-[Describe workflow purpose and capabilities]
-
-## Process
-[Detail step-by-step workflow execution]
-
-## Tool Integration
-[Specify Windsurf tool coordination]
-
-## Output Organization
-[Define file structure and locations]
-```
-
-### Rule Customization
-
-Enhance `.windsurf/rules/cc.md` with team-specific guidelines:
-
-```markdown
-## Team-Specific Rules
-
-### Code Standards
-[Define team coding standards]
-
-### Review Process
-[Specify review requirements]
-
-### Documentation Standards
-[Define documentation expectations]
-```
-
-### Workflow Chaining
-
-Chain workflows for complex development processes:
-
-1. **Initialize** → **Research** → **Create ADR**
-2. **Create Spec** → **Execute Task** → **Status Check**
-3. **Explain Code** → **Swab** → **Status Update**
-
-## 🔧 Configuration
-
-### Windsurf Settings
-Configure Windsurf to optimize Code Captain integration:
-
-- **Enable advanced context management**
-- **Configure AI coordination preferences**
-- **Set up workspace awareness**
-
-### Project-Specific Rules
-Customize `.windsurf/rules/cc.md` for your project:
-
-- **Domain-specific guidelines**
-- **Technology-specific patterns**
-- **Team collaboration standards**
-
-## 📊 Workflow Reference
-
-| Workflow | Purpose | Output Location |
-|----------|---------|-----------------|
-| `initialize` | Project analysis & setup | `.code-captain/docs/` |
-| `create-spec` | Feature specification | `.code-captain/specs/` |
-| `execute-task` | TDD implementation | Source code + tests |
-| `create-adr` | Architecture decisions | `.code-captain/decision-records/` |
-| `status` | Project health analysis | Terminal output |
-
-## 🛠️ Troubleshooting
-
-### Workflows Not Executing Properly
-**Problem**: Windsurf doesn't follow workflow steps correctly  
-**Solution**: Ensure workflow files are in `.windsurf/workflows/` and reference them explicitly
-
-### Context Issues
-**Problem**: AI loses context during workflow execution  
-**Solution**: Break complex workflows into smaller steps and verify context preservation
-
-### File Organization Problems
-**Problem**: Generated files appear in wrong locations  
-**Solution**: Check `.code-captain/` folder structure and verify workflow output specifications
-
-## 🤝 Contributing
-
-Windsurf-specific contributions:
-
-1. **Workflow Enhancement** - Improve AI coordination and workflow efficiency
-2. **Rule Development** - Add domain-specific rules and guidelines
-3. **Documentation** - Create Windsurf-specific examples and patterns
-4. **Integration** - Enhance Windsurf AI coordination capabilities
-
----
-
-**Ready to supercharge your Windsurf development?**
-
-1. **Install:** `npx @devobsessed/code-captain`
-2. **Reference:** `.windsurf/workflows/initialize.md`
-3. **Begin:** Project initialization workflow 

package/windsurf/rules/cc.md

@@ -1,5 +0,0 @@
----
-trigger: always_on
----
-
-some content