| name | codeflow-maintainer |
| description | OpenClaw-only maintainer PR workflow modes and skills. For OpenCoven/coven PR creation, redirect to skills/pr-agent, the Coven PR Readiness Agent.
|
| version | 1.0.0 |
| tags | ["github","pr","workflow","maintainer","code-review","openclaw"] |
| inheritable | true |
CodeFlow Maintainer Skill
Source of Truth
PR_WORKFLOW.md: https://github.com/openclaw/maintainers/blob/main/.agents/skills/PR_WORKFLOW.md
This skill is OpenClaw-only. It implements the workflow defined in
openclaw/maintainers for OpenClaw repositories. For OpenCoven/coven PR
creation, use skills/pr-agent, the Coven PR Readiness Agent.
Working Rule
Skills execute workflow. Maintainers provide judgment.
Always pause between skills to evaluate technical direction, not just command success.
Workflow Modes
1. Triage
Purpose: Assess whether PR is worth reviewing.
Focus:
- Is the problem statement clear?
- Does a realistic verification path exist?
- Is this PR worth our time?
- Are there duplicates?
Recommendation: Proceed to Review, Request Info, or Close.
Agent prompt:
[Mode: TRIAGE] Assess whether this PR is worth reviewing.
Focus on problem clarity, scope match, duplicate detection.
DO NOT suggest code changes, approvals, or merges.
2. Review (review-pr)
Purpose: Review only — produce findings and recommendation. DO NOT modify code.
Quality bar:
- Do not trust PR code by default
- Keep types strict (no
any)
- Evaluate security impact and abuse paths
- Understand the system before changing it
Finding severities:
BLOCKER — must fix before prepareIMPORTANT — must fix before prepareMINOR — should fix (optional)NOTE — informational only
Artifacts: .local/review.md, .local/review.json
Checkpoint before advancing:
- What problem are they trying to solve?
- What is the most optimal implementation?
- Can we fix up everything?
- Do we have any questions?
Agent prompt:
[Mode: REVIEW] Produce findings, DO NOT modify code.
Focus: correctness, security, tests, types, scope, hardening.
Severity: BLOCKER > IMPORTANT > MINOR > NOTE.
Recommendation: READY FOR PREPARE, NEEDS WORK, NEEDS DISCUSSION, or CLOSE.
3. Prepare (prepare-pr)
Purpose: Make PR merge-ready on its head branch.
Order: Rebase → Fix BLOCKER/IMPORTANT → Changelog → Gates → Push
Gates: pnpm build, pnpm check, pnpm test
Rules:
- Rebase onto main FIRST before any fixes
- Add changelog entry with
(#PR) and thanks @author
- Push to PR head branch only, NEVER to main
- Use
scripts/committer for commits
Checkpoint before advancing:
- Most optimal implementation?
- Properly scoped and reusing existing logic?
- Properly typed and hardened?
- Enough meaningful tests? (fake timers where appropriate)
- Any security vulnerabilities introduced?
- Follow-up refactors to defer?
Agent prompt:
[Mode: PREPARE] Make PR merge-ready. Rebase first, then fix, then gates.
Push to PR head branch only, never to main.
Gates: pnpm build, pnpm check, pnpm test.
4. Merge (merge-pr)
Purpose: Final verification and squash-merge.
Go/no-go checklist:
- All BLOCKER and IMPORTANT findings resolved
- Meaningful verification, low regression risk
- Changelog updated with PR # and thanks @author
- CI green, branch not behind main
Merge method: Squash with Co-authored-by: trailers for PR author + maintainer.
Post-merge: Verify PR reaches MERGED state. Post comment with merge SHA.
Agent prompt:
[Mode: MERGE] All gates must be green. Squash merge with Co-authored-by.
Verify MERGED state. Post comment with SHA.
DO NOT modify code — go back to Prepare if needed.
5. Post-Merge
Purpose: Cleanup, attribution, follow-ups.
Tasks:
- Delete branch
- Update clawtributors for new contributors (
bun scripts/update-clawtributors.ts)
- Create follow-up issues for deferred refactors
- Clean up worktree
Mode Transitions
Triage → Review → Prepare → Merge → Post-Merge
↑___________↓ (back to Prepare if changes needed)
- Each transition requires checkpoint questions answered
- Modes cannot be skipped (triage → prepare is not valid)
read-only overrides everything when active
Related Skills
PR Agent Orchestrator
For concrete workflow execution, see the pr-agent skill:
- OpenClaw: use the OpenClaw maintainer skill bundle.
- OpenCoven/coven: use
skills/pr-agent, the Coven PR Readiness Agent.
The pr-agent skill provides:
- Automatic artifact validation (
.local/*.json, .local/*.md)
- Script wrapper invocation (
scripts/pr-review, scripts/pr-prepare, scripts/pr-merge)
- Checkpoint enforcement between phases
- Escalation trigger detection
Inheritable Skills
This skill is designed to be inherited by other agents:
Agents inheriting this skill should:
- Follow the mode progression strictly
- Use the checkpoint questions before advancing
- Inject the mode-specific prompt into their system context
- Respect the quality bar (types, security, tests, scope)
