github-workflow-automation

Run npx ruv-swarm actions generate-workflow with the --analyze-codebase and --detect-languages flags to inspect your repository and produce an optimized pipeline. The generated workflow is written to .github/workflows and can include caching and parallelization.

Use gh run view with the run ID to fetch job data, then pipe it into npx ruv-swarm actions analyze-failure with --suggest-fixes. The tool classifies the failure and can auto-retry flaky steps or propose fixes.

You need the GitHub CLI (gh) authenticated, git, Node.js v16 or later, and the claude-flow@alpha package. The repository must have GitHub Actions enabled and a .github/workflows directory.

Yes, dedicated modes like pr-manager, code-reviewer, and release-manager coordinate multi-agent PR validation, semantic versioning, changelog generation, and multi-stage deployments. They integrate with gh commands for comments and status checks.

Yes, it can detect changed packages in a monorepo and build them via a dynamic matrix, and the sync-coordinator mode aligns versions and creates PRs across multiple repositories. The repo-architect mode also optimizes repository structure.

Common causes are missing dependency caching, redundant steps, oversized runners, and poor parallelization. The analytics and cost-optimize commands identify bottlenecks, suggest caching strategies, and recommend appropriate runner sizes.