| name | workflow-monitor |
| description | Detects workflow failures and inefficient patterns then files GitHub issues. Use when a workflow step repeatedly fails or produces inconsistent output. |
| alwaysApply | false |
| category | workflow-methodology |
| tags | ["workflow","monitoring","error-detection","efficiency","automation"] |
| dependencies | ["leyline:git-platform","imbue:proof-of-work","sanctum:fix-workflow"] |
| tools | [] |
| usage_patterns | ["error-detection","efficiency-analysis","issue-creation"] |
| complexity | intermediate |
| model_hint | standard |
| estimated_tokens | 2500 |
| modules | ["modules/detection-patterns.md","modules/issue-templates.md","modules/efficiency-metrics.md"] |
When NOT To Use
- A one-off failure worth debugging directly (use
superpowers:systematic-debugging)
- Rewriting the workflow's assets (use
sanctum:workflow-improvement)
Table of Contents
Workflow Monitor
Monitor workflow executions for errors and inefficiencies, automatically creating issues on the detected git platform (GitHub/GitLab) for improvements. Check session context for git_platform: and use Skill(leyline:git-platform) for CLI command mapping.
Philosophy
Workflows should improve over time. When execution issues occur, capturing them systematically enables continuous improvement. This skill hooks into workflow execution to detect problems and propose fixes.
Quick Start
Manual Invocation
/workflow-monitor --analyze-last
/workflow-monitor --session <session-id>
/workflow-monitor --efficiency-report
Automatic Monitoring (via hooks)
When enabled, workflow-monitor observes execution and flags:
- Command failures (exit codes > 0)
- Timeout events
- Repeated retry patterns
- Context exhaustion
- Inefficient tool usage
Detection Patterns
Error Detection
| Pattern | Signal | Severity |
|---|
| Command failure | Exit code > 0 | High |
| Timeout | Exceeded timeout limit | High |
| Retry loop | Same command >3 times | Medium |
| Context exhaustion | >90% context used |
