Pull requests, review and gates
How Skaftor raises pull requests, reviews them with AI, gates them on CI and acceptance criteria, and lets you approve and merge — one at a time or a whole feature at once.
Raising the pull request
Cloud agents open the pull request themselves. When a work order is "Ready for a pull request", select "Raise pull request" — skaftorAI drafts the title and description, which you can edit before "Create pull request".
AI review
When a coding agent opens a pull request, the AI review runs automatically (or select "Run AI review"). It gives a verdict — "Looks good", "Changes requested" or "Commented" — a score out of 100, the acceptance criteria met, and findings by severity with a suggested fix.
The pull-request gate
A work order isn't done until its gate passes. The gate reads the pull request's CI checks first, then a clause judge reads the diff — never the agent's summary — against the acceptance criteria. If something needs judgement the gate is "held — needs a person". "Gate now" re-runs it.
Configure it in Settings › "AI keys & limits" › "Pull requests": whether CI is required, whether AI checks the code against the PRD, and how long to wait for tests.
Approve and merge
Open the diff, then "Approve" and "Merge PR" from the work order. Skaftor won't merge an unapproved pull request, and the author can't approve their own. To finish a feature, use "Approve & merge all" on its Build tab — it merges in phase order and skips work orders without a pull request.
If changes are requested or the pull request is closed, select "Execute again" to run the work order again.
Branches and releases
Settings › "Workflow" sets how code reaches release: "Feature branch" (recommended — work-order PRs merge into a feature branch, then on to release), "Trunk + feature flags", or an "Integration branch". With feature branches, Skaftor opens one release pull request per repository when QA Approval passes — a person merges those; Skaftor never does.