octo-sentinel

Sentinel (/octo:sentinel)

MANDATORY COMPLIANCE — DO NOT SKIP

When the user invokes /octo:sentinel, you MUST execute the structured triage workflow below. You are PROHIBITED from:

• Manually checking GitHub status without running the sentinel pipeline
• Skipping the triage scan and just reading gh output directly
• Deciding there's "nothing to triage" without actually running the checks
• Substituting a quick gh pr list for the full sentinel workflow

The user chose /octo:sentinel for structured, prioritized triage — not a raw gh dump.

---

Your first output line MUST be: 🐙 Octopus Sentinel

GitHub-aware work monitor that triages issues, PRs, and CI failures. Sentinel observes and recommends workflows but never auto-executes them.

Usage

/octo:sentinel              # One-time triage scan
/octo:sentinel --watch       # Continuous monitoring
/octo:sentinel --canary      # Post-deploy canary monitoring
/octo:sentinel --canary URL  # Monitor specific URL after deploy

What Sentinel Monitors

Source	Filter	Recommended Action
Issues	octopus label	Classified via task type → workflow recommendation
PRs	Review requested	/octo:ink for code review
CI Runs	Failed status	/octo:debug for investigation
Deployments	Post-deploy health	Canary alerts → /octo:debug

Canary Mode (Post-Deploy Monitoring — Auto-Triggered)

Auto-trigger: Canary runs automatically when:

• The /octo:deliver phase completes successfully (post-validation health check)
• Sentinel --watch mode detects a new deployment via gh api (deployment event)
• The user runs git push to a branch with an active Vercel/Netlify/Railway deployment

No manual --canary flag needed — sentinel detects deployments and starts monitoring.

When invoked explicitly with --canary, or auto-triggered, sentinel switches to post-deploy health monitoring:

1. Detect deployment — reads the latest Vercel/GitHub deployment or uses the URL argument
2. Baseline capture — screenshots + console output + performance timing from pre-deploy (or first run)
3. Health checks (runs every 60s for 5 minutes, then every 5 minutes):
   • Page loads without errors (HTTP 200, no uncaught exceptions)
   • Console error detection (new errors not in baseline)
   • Core Web Vitals regression (LCP, CLS, FID compared to baseline)
   • Key UI elements render (checks for empty/broken layouts)
4. Alert on anomalies — if any check fails, sentinel reports:

   🐙 Sentinel Canary Alert
   ⚠ [anomaly type]: [description]
   Baseline: [expected]  |  Current: [observed]
   Recommendation: /octo:debug "[anomaly description]"
   

5. Results — written to .octo/sentinel/canary-<timestamp>.md