Docs agents that each
own one job
Every agent watches for one kind of change, writes the docs update and opens a pull request. The review agent checks each one before anything merges.
Merged code, updated docs
When a product PR merges, Paperkraft reads the diff, finds every page that describes that behaviour and opens a docs PR with the change and the reason.
- Starts when
- PR merged in a product repo
- You get
- Docs PR with a written reason
- Maps code changes to the pages they affect
- Edits every version that needs it
- Skips internal changes nobody reads about
New feature, first draft ready
A new endpoint or module gets a first-draft page in your house style, with a working example and its place in the sidebar. Your team edits instead of starting from blank.
- Starts when
- New endpoint, SDK method or ticket
- You get
- Draft page and sidebar entry
- Learns tone from your existing docs
- Follows your style guide and Vale rules
- Updates sidebars.js, SUMMARY.md or meta.json
No broken links, week after week
A scheduled crawl checks every internal link, anchor and redirect. Paperkraft fixes what it finds and batches it all into one small, safe PR.
- Starts when
- Schedule, or any docs PR
- You get
- One tidy fix PR
- Internal links, anchors and external URLs
- Adds redirects when pages move
- Low risk, so it can merge on its own
Decided in Slack, fixed in the docs
Mention @Paperkraft in the thread where the decision happened. It finds every page that says otherwise, fixes them and replies with the PR.
- Starts when
- @Paperkraft in Slack, Jira or Linear
- You get
- PR link, replied in thread
- Understands the whole thread
- Asks the author when something is unclear
- Weekly digest to a channel
Start with Docs sync
Most teams switch on Docs sync first. Join the beta and we will help you set it up on your docs repository.