| name | pr-maintainer |
| description | Maintain an agent-created pull request after creation or after draft-to-ready transition: mark reviewable draft PRs ready, poll CI and review comments with gh, repair failures in the same worktree/session, reply in Japanese, escalate design loops, and squash merge when safe. This skill defines the maintenance POLICY (what to repair, when to merge/escalate); the autonomous re-polling LOOP that reschedules itself without human restarts lives in pr-autoloop. Use after creating PRs or when asked to continue PR maintenance automation. |
| metadata | {"short-description":"PR作成後のCI/レビュー監視、修正、返信、設計エスカレーション、squash mergeを共通運用する。"} |
| dependencies | ["github-ops"] |
PR Maintainer
Follow the repository's PR maintenance policy/ADR, if one exists, when maintaining a PR created by Codex or
Claude Code.
When to Use
Use this skill after an agent creates a PR, including a draft PR, or when asked to continue an
agent-created PR through CI, review comments, repair commits, and merge.
Also use this skill immediately after an agent-created draft PR becomes ready for review, even when the
ready-for-review transition was performed manually by the user outside the agent session. Treat that transition
as the start signal for CI and review-state monitoring.
If the PR was opened as draft only because repository workflow says to create draft PRs, and the implementation
has already passed the repository's agreed local validation (see the project's testing rules for the exact
CI-equivalent filter), mark it ready for review in the same session and immediately enter the polling workflow.
Do not leave a reviewable draft PR idle just because it was created with .
