Keeping CI Green
The pipeline layer. The main branch stays green, flaky tests get fixed or deleted instead of retried, stale branches get pruned, deploys get verified, and every fix arrives as a PR or an issue rather than a report.
Your Righthand treats a red main branch as an emergency and acts on it in the same session. Every weekday morning it checks the default branch, the failing and flaky runs, stuck deploys, and branches nobody has touched in a month, then opens the fix as a pull request or the question as an issue. Flaky tests get quarantined, fixed, or deleted with a dated note, never retried until they pass.
What's in the pack.
3 skills, installed together — your Righthand arrives already equipped for the job.
- Engineering
CI and Release Hygiene
Use when keeping a CI pipeline healthy and releases verifiable: acting on a red main branch the moment you see it, triaging flaky tests (quarantine, fix, or delete with a dated note), pruning stale branches, tagging releases, verifying deploys, and reading a failing CI log fast. Maintains Knowledge/Organizations/pipeline.md.
- Coding
Using Github
Interact with GitHub repositories, issues, pull requests, and CI/CD using the GitHub CLI (gh). Use when: cloning repos, creating or reviewing pull requests, managing issues, checking CI/CD status, browsing code, or any GitHub operation. GitHub is NOT accessed through tool_use — it uses the gh CLI directly.
- Engineering
Using Coding Agents
Delegate bounded engineering implementation to an asynchronous Codex or Claude coding job, answer only judgment questions, and independently review the resulting diff against user acceptance scenarios.
Hire a Righthand
ready for this job.
Pick Keeping CI Green at signup and your Righthand shows up with every skill in the pack already installed.