What problem does it solve?
OpenShell maintainers need consistent triage, review, and merge-readiness tracking across GitHub issues and pull requests, and manual label management and follow-up monitoring is error-prone and time-consuming.
Core Features & Use Cases
- State-machine gating: Drives issues and PRs through gator:* labels (follow-up-needed, blocked, validated, in-review, watch-pipeline, approval-needed, merge-ready) with defined transitions and 48-business-hour TTL nudges.
- Durable review tracking: Uses a review-feedback ledger with stable finding IDs to carry findings across head SHAs, resolve addressed review threads, and avoid duplicate reviews.
- Supervised watch mode: Emits OPENSHELL_AGENT_RESULT sentinels so the OpenShell agent supervisor can poll PRs until merge, close, or blocker resolution.
- Use Case: A maintainer asks the agent to gate PR #412; the skill validates it, posts a marked review disposition, applies gator:in-review, monitors CI, and advances it to gator:merge-ready once checks are green and approval arrives.
Quick Start
Ask the agent to run gator on a specific OpenShell issue or PR number, for example: validate and monitor PR 412 until it is merge-ready.