dev-workflowlisted

<Purpose> Automate common developer workflows that span multiple tools and data sources -- GitHub PRs, CI pipelines, error tracking, code metrics, and system health. This skill gathers information from disparate sources in parallel, cross-references it (which commits caused which errors, which PRs affect which issues), generates actionable developer reports, and sends critical alerts. It replaces the manual morning routine of checking GitHub, CI, Sentry, and Slack. </Purpose> <Use_When> - User says "check PRs", "CI status", "what's the deploy status?" - User asks "code metrics", "developer report", "project health" - User says "what happened while I was away?", "catch me up", "morning brief" - User wants to review pull requests with context from CI and error tracking - User asks "which commits broke the build?", "what errors are new?" - User wants to track deployment status or release readiness - User says "dev report", "status report", "weekly summary" </Use_When> <Do_Not_Use_When> - Pure code editing or implementation -- use executor agents or `ralph` instead - Git operations only (commit, branch, merge) -- use `git-master` skill instead - Deep code analysis or architecture review -- use `analyze` skill instead - Debugging a specific bug -- use `analyze` or delegate to architect agent - Writing documentation -- use writer agent instead </Do_Not_Use_When> <Why_This_Exists> Developers waste 30-60 minutes daily checking multiple tools for status updates. GitHub notification