ctx-cc 3.0.0 → 3.3.0

package/commands/monitor.md

@@ -0,0 +1,474 @@
+---
+name: monitor
+description: Self-healing deployments - connect to error tracking (Sentry/LogRocket), auto-create fix stories, and optionally auto-fix with PR creation.
+---
+
+<objective>
+CTX 3.3 Self-Healing Deployments - Monitor production errors and automatically create fix stories or even auto-fix with PR creation.
+</objective>
+
+<usage>
+```
+/ctx monitor                    # Show monitoring status
+/ctx monitor connect sentry     # Connect Sentry integration
+/ctx monitor connect logrocket  # Connect LogRocket integration
+/ctx monitor errors             # List recent errors
+/ctx monitor auto-fix [id]      # Auto-fix specific error
+/ctx monitor --watch            # Continuous monitoring mode
+```
+</usage>
+
+<workflow>
+
+## Step 1: Connect Error Tracking
+
+### Sentry Integration
+```bash
+/ctx monitor connect sentry
+```
+
+Prompts for:
+- Sentry DSN or API token
+- Organization slug
+- Project slug
+- Environment filter (production, staging, etc.)
+
+Stores in `.ctx/config.json`:
+```json
+{
+  "monitor": {
+    "sentry": {
+      "enabled": true,
+      "token": "env:SENTRY_AUTH_TOKEN",
+      "organization": "my-org",
+      "project": "my-app",
+      "environment": "production"
+    }
+  }
+}
+```
+
+### LogRocket Integration
+```bash
+/ctx monitor connect logrocket
+```
+
+Stores in `.ctx/config.json`:
+```json
+{
+  "monitor": {
+    "logrocket": {
+      "enabled": true,
+      "appId": "my-org/my-app",
+      "apiKey": "env:LOGROCKET_API_KEY"
+    }
+  }
+}
+```
+
+## Step 2: Fetch Errors
+
+Poll error tracking service:
+
+```
+[MONITOR] Fetching errors from Sentry...
+
+Recent Errors (last 24h):
+
+ID        | Error                          | Count | Users | First Seen
+----------|--------------------------------|-------|-------|------------
+ERR-001   | TypeError: Cannot read 'id'    | 45    | 12    | 2h ago
+ERR-002   | NetworkError: Failed to fetch  | 23    | 8     | 4h ago
+ERR-003   | ValidationError: Invalid email | 15    | 15    | 6h ago
+ERR-004   | 500: Internal Server Error     | 8     | 5     | 12h ago
+
+Actions:
+  [1] View ERR-001 details
+  [2] Create fix story for ERR-001
+  [A] Auto-fix ERR-001 (creates PR)
+```
+
+## Step 3: Error Analysis
+
+When viewing error details:
+
+```
+[MONITOR] Error Details: ERR-001
+
+Type: TypeError
+Message: Cannot read properties of undefined (reading 'id')
+File: src/components/UserProfile.tsx:45
+Function: UserProfile
+
+Stack Trace:
+  at UserProfile (src/components/UserProfile.tsx:45:23)
+  at renderWithHooks (node_modules/react-dom/...)
+  at mountIndeterminateComponent (...)
+
+Context:
+  - URL: /users/123/profile
+  - Browser: Chrome 120
+  - User: authenticated
+  - Session: 5 minutes
+
+Similar Errors:
+  - 3 occurrences in UserSettings.tsx (same pattern)
+  - Last occurred: 15 minutes ago
+
+Suggested Fix:
+  Add null check: user?.id instead of user.id
+  Or add loading state guard
+
+Actions:
+  [F] Create fix story
+  [A] Auto-fix and create PR
+  [I] Ignore (mark as expected)
+```
+
+## Step 4: Create Fix Story
+
+Automatically generate story from error:
+
+```json
+{
+  "id": "S-FIX-001",
+  "title": "Fix TypeError in UserProfile component",
+  "type": "fix",
+  "priority": "high",
+  "source": "sentry",
+  "errorId": "ERR-001",
+  "description": "TypeError: Cannot read properties of undefined (reading 'id') in UserProfile.tsx:45",
+  "acceptance": [
+    "Error no longer occurs on /users/*/profile pages",
+    "Proper loading state shown while user data loads",
+    "Null check added for user object",
+    "Similar pattern fixed in UserSettings.tsx",
+    "Error rate drops to 0 for this issue"
+  ],
+  "context": {
+    "file": "src/components/UserProfile.tsx",
+    "line": 45,
+    "errorCount": 45,
+    "affectedUsers": 12,
+    "stackTrace": "..."
+  },
+  "suggestedFix": "Add optional chaining: user?.id"
+}
+```
+
+## Step 5: Auto-Fix Mode
+
+For simple errors, auto-fix with PR:
+
+```
+[MONITOR] Auto-Fix: ERR-001
+
+Analyzing error...
+  ✓ Pattern identified: Missing null check
+  ✓ Fix available: Add optional chaining
+  ✓ Similar locations found: 2 files
+
+Generating fix...
+  ✓ Modified: src/components/UserProfile.tsx
+  ✓ Modified: src/components/UserSettings.tsx
+  ✓ Added loading state guard
+
+Verification:
+  ✓ TypeScript compiles
+  ✓ Tests pass
+  ✓ No new errors introduced
+
+Creating PR...
+  ✓ Branch: fix/err-001-userprofile-null-check
+  ✓ PR: #123 - Fix TypeError in UserProfile
+
+[MONITOR] Auto-fix complete!
+
+PR: https://github.com/org/repo/pull/123
+Review required before merge.
+
+Slack notification sent to #dev-alerts.
+```
+
+</workflow>
+
+<auto_fix_rules>
+
+## Safe Auto-Fix Patterns
+
+CTX can auto-fix these patterns:
+
+| Pattern | Fix | Risk |
+|---------|-----|------|
+| Missing null check | Add optional chaining | Low |
+| Undefined property | Add default value | Low |
+| Missing import | Add import statement | Low |
+| Type mismatch | Add type assertion | Medium |
+| Missing error handling | Add try/catch | Medium |
+| Race condition | Add async guard | Medium |
+
+## Requires Human Review
+
+These need human approval:
+
+| Pattern | Reason |
+|---------|--------|
+| Logic errors | Business logic understanding needed |
+| Security issues | Careful review required |
+| Database changes | Migration risk |
+| API changes | Breaking change risk |
+| Performance issues | Optimization choices |
+
+## Auto-Fix Process
+
+```
+1. Identify error pattern
+2. Check if pattern is in safe list
+3. If safe:
+   a. Generate fix
+   b. Run tests
+   c. Create PR
+   d. Notify team
+4. If not safe:
+   a. Create fix story
+   b. Assign to on-call
+   c. Provide context
+```
+
+</auto_fix_rules>
+
+<continuous_monitoring>
+
+## Watch Mode
+
+```bash
+/ctx monitor --watch
+```
+
+Continuous monitoring with alerts:
+
+```
+[MONITOR] Watching production errors...
+
+Press Ctrl+C to stop.
+
+[10:30:15] New error: TypeError in checkout.ts
+  → Creating fix story S-FIX-002
+  → Slack alert sent
+
+[10:45:00] Error spike detected: NetworkError (50 in 5min)
+  → Possible API outage
+  → Escalating to #incidents
+
+[11:00:00] Error resolved: ERR-001 (no occurrences in 30min)
+  → Closing related story
+
+[11:15:00] Auto-fixed: Simple null check in profile.ts
+  → PR #124 created
+  → Awaiting review
+```
+
+## Alert Rules
+
+`.ctx/config.json`:
+```json
+{
+  "monitor": {
+    "alerts": {
+      "errorSpike": {
+        "threshold": 50,
+        "window": "5m",
+        "action": "escalate"
+      },
+      "newError": {
+        "action": "create-story"
+      },
+      "criticalError": {
+        "keywords": ["payment", "auth", "security"],
+        "action": "page-oncall"
+      }
+    }
+  }
+}
+```
+
+</continuous_monitoring>
+
+<integrations>
+
+## Error Tracking Services
+
+### Sentry
+```json
+{
+  "sentry": {
+    "enabled": true,
+    "token": "env:SENTRY_AUTH_TOKEN",
+    "organization": "org-slug",
+    "project": "project-slug",
+    "environment": "production",
+    "issueUrl": "https://sentry.io/organizations/{org}/issues/{id}/"
+  }
+}
+```
+
+API Usage:
+- List issues: `GET /api/0/projects/{org}/{project}/issues/`
+- Get issue: `GET /api/0/issues/{id}/`
+- Get events: `GET /api/0/issues/{id}/events/`
+
+### LogRocket
+```json
+{
+  "logrocket": {
+    "enabled": true,
+    "appId": "org/app",
+    "apiKey": "env:LOGROCKET_API_KEY",
+    "sessionUrl": "https://app.logrocket.com/{appId}/sessions/{id}"
+  }
+}
+```
+
+### Bugsnag
+```json
+{
+  "bugsnag": {
+    "enabled": true,
+    "apiKey": "env:BUGSNAG_API_KEY",
+    "projectId": "project-id"
+  }
+}
+```
+
+### Datadog
+```json
+{
+  "datadog": {
+    "enabled": true,
+    "apiKey": "env:DD_API_KEY",
+    "appKey": "env:DD_APP_KEY",
+    "site": "datadoghq.com"
+  }
+}
+```
+
+## Notification Services
+
+### Slack
+```json
+{
+  "notifications": {
+    "slack": {
+      "webhook": "env:SLACK_WEBHOOK_URL",
+      "channels": {
+        "errors": "#dev-errors",
+        "incidents": "#incidents",
+        "fixes": "#auto-fixes"
+      }
+    }
+  }
+}
+```
+
+### PagerDuty
+```json
+{
+  "notifications": {
+    "pagerduty": {
+      "routingKey": "env:PAGERDUTY_ROUTING_KEY",
+      "severityMapping": {
+        "critical": "critical",
+        "high": "error",
+        "medium": "warning"
+      }
+    }
+  }
+}
+```
+
+</integrations>
+
+<output_format>
+
+## Status Output
+```
+[MONITOR] Production Monitoring Status
+
+Services Connected:
+  ✓ Sentry (my-org/my-app)
+  ○ LogRocket (not configured)
+  ○ Bugsnag (not configured)
+
+Last 24 Hours:
+  Errors: 91 (↓15% from yesterday)
+  Unique: 4 error types
+  Users affected: 40
+  Auto-fixed: 2
+
+Active Issues:
+  ERR-001: TypeError in UserProfile (45 occurrences)
+  ERR-002: NetworkError (23 occurrences)
+
+Recent Auto-Fixes:
+  PR #123: Null check in profile.ts (merged)
+  PR #124: Loading state in dashboard.tsx (pending)
+
+Monitoring: Active
+Watch mode: /ctx monitor --watch
+```
+
+## Error Alert
+```
+[MONITOR] 🚨 New Production Error
+
+Type: TypeError
+Message: Cannot read 'id' of undefined
+File: src/checkout.ts:78
+Users: 5 affected
+First seen: 2 minutes ago
+
+Quick actions:
+  [V] View details
+  [F] Create fix story
+  [A] Auto-fix
+  [I] Ignore
+```
+
+</output_format>
+
+<configuration>
+
+## Full Monitor Config
+
+`.ctx/config.json`:
+```json
+{
+  "monitor": {
+    "enabled": true,
+    "pollInterval": "5m",
+    "autoFix": {
+      "enabled": true,
+      "safePatterns": ["null-check", "import-missing", "type-mismatch"],
+      "requireReview": true,
+      "createPR": true
+    },
+    "alerts": {
+      "slack": true,
+      "pagerduty": false,
+      "email": false
+    },
+    "ignore": {
+      "patterns": ["ResizeObserver", "Script error"],
+      "environments": ["development", "staging"]
+    },
+    "sentry": {
+      "enabled": true,
+      "token": "env:SENTRY_AUTH_TOKEN",
+      "organization": "my-org",
+      "project": "my-app"
+    }
+  }
+}
+```
+
+</configuration>