steward
SolidDrive a pull request on this repository to green — which fast checks to run before pushing, how to read a red check, and what to do about a review comment. Use when a CI failure, a review comment, a merge conflict, or a scheduled check-in arrives on a PR you opened or were asked to drive.
Install
Quality Score: 83/100
Skill Content
Details
- Author
- yschimke
- Repository
- yschimke/compose-ai-tools
- Created
- 5 months ago
- Last Updated
- today
- Language
- Kotlin
- License
- Apache-2.0
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
green
Get a PR green. Rebase it on its base branch, fix the easy red, ask about the rest, amend into the commit that owns the change, force-push, and watch CI until it passes. Use when a PR is red or has fallen behind, and never for review threads, which are somebody's words rather than a failing check.
committing
Pre-commit and pre-push checklist for the owner's public GitHub repos. Run before every commit, push, or PR, even a one-line change or a plain "push this". Covers the Git workflow (branch/PR or direct-to-main per the lock, conventional commits), comment pruning, and docs/CLAUDE.md/CHANGELOG upkeep.
happier-pr-steward
Analyze and shepherd a Happier pull request from intent review through approved refinements, current-head CI and review follow-up, evidence-based comment adjudication, and any required intent-preserving version-line port. Use when asked to assess whether a PR is correct or mergeable, detect duplicate or split-brain logic, add follow-up commits, request or monitor reviews, address PR feedback, or carry a 0.2 PR and every accepted follow-up into the evolved 0.3 line.