The checks that make
docs automation safe
Every change an agent writes is built, link checked, style checked and scored for risk by a separate review agent. You decide what can merge without you.
A second agent checks the first
The agent that writes never approves its own work. An independent reviewer checks every change, scores the risk and decides: merge now, merge in 24 hours, or a named human.
- Starts when
- Every PR any agent opens
- You get
- Risk score and routing
- Build, link and style checks run first
- Risk from size, location and change type
- Starts in Co-pilot until you trust it
Autopilot by risk, not all or nothing
Every change gets a risk level from what it touches. You choose how much can merge on its own, and you can change it any time.
Small, safe fixes merge after checks. Small edits merge after 24 hours unless someone objects. Anything bigger waits for a person.
Broken links, typos, redirects, sidebar order
Merges after checksSmall edits under 30 lines, renamed parameters
Merges in 24hNew or deleted pages, API behaviour, pricing, security
Waits for a personStarts wherever the work happens
Agents run on the events your team already produces. There is nothing new to remember.
A pull request merges
Docs sync reads the diff in any product repo you connect.
A ticket closes
Label a ticket docs-needed and it becomes a docs change when it closes.
Someone asks in a thread
Mention @Paperkraft where the decision was made.
A schedule runs
Weekly link checks, monthly freshness reviews, whatever cadence you set.
Everything shipped, in one message
Once a week Paperkraft posts what changed in your docs, what merged on its own and what is waiting for someone. Leads read one message instead of every pull request.
- Sent to a Slack channel or by email
- Links to every pull request it mentions
- Anything reverted, and by whom
PaperkraftMonday, #docs- 14 merged after checks
- 3 merged after 24 hours
- 2 approved by your team
- 1 reverted in one click
Start in Co-pilot
Nothing merges without your approval until you decide it should. Join the beta to try it on your own docs.