A review board for GitBook change requests across every space
See every open docs edit from all your spaces in one queue, with the oldest floating to the top, and approve, comment, or merge without leaving the page.
GitBook
Slack BotProductOperationsResearch & MonitoringContent GenerationBuild me an app my documentation team opens every morning to clear the change request queue across all of our GitBook spaces. GitBook makes you check each space separately, so edits sit in review and quietly rot. This app should be the one surface where the whole queue is visible and reviewable.
The main view is a single review board listing every open change request across the organization. Load it by calling List Organization Spaces to get every space, then List Change Requests for each space, keeping the ones that are still open or in review. Each row shows the change request subject, its author, the target space, how many days it has been open (counted from its created date), and its current review state such as draft, in review, approved, or changes requested. Default the sort to oldest first. Include an aging filter with a threshold that defaults to five days, so anything sitting longer than five days floats to the top of the board and is visually marked as overdue. Also give me filters by space, by author, and by review state, and paginate the underlying calls since a busy organization will have many spaces.
Show a stale badge on any change request whose base content has drifted since it was opened, because those are the ones that merge badly. Work this out by comparing the revision the change request was branched from against the current live revision of its space, using Get Change Request for the request details and Get Space for the space's current state. When a request is stale, offer a Sync with primary action on the row and in the detail view that calls Sync Change Request With Primary to pull the live changes into the request, and refresh the badge afterwards.
Clicking a row opens a detail view for that change request. Use Get Change Request for the metadata, then show the pages the edit touches by calling List Pages In Space scoped to the change request and Get Page By ID for each changed page, requesting markdown so the content renders readably. Show the full comment thread alongside the pages using List Change Request Comments, so a reviewer sees the discussion and the content side by side without switching context.
From that detail view a reviewer can act on the request directly. Posting a comment calls Post Change Request Comment. Approving or requesting changes calls Submit Change Request Review. Merging calls Merge Change Request, and the app should surface failures clearly rather than silently: if the merge is blocked because the space requires approvals that are not in yet, or because the request has conflicts, say so in plain language and point the reviewer at the Sync with primary action. There is also a nudge action that pings the author in Slack: look the author up with Look Up User by Email, then Send a Message with the change request subject, how long it has been waiting, and a link back to this app.
Add a Review with AI button on the detail view that kicks off a background agent for that change request. The agent reads the changed pages with Get Page By ID, then searches the rest of the published documentation with Search Organization Content looking for statements that this edit now contradicts, for example an older page still describing the behaviour the edit is changing. It also checks cross references and terminology against neighbouring pages in the same space using List Pages In Space and Get Page By ID, so it catches links that will break and wording that no longer matches the house vocabulary. When it finishes it posts its findings as a comment on the change request with Post Change Request Comment, and writes the verdict back into the app so the human sees it inline on the detail view before merging, plus a small indicator on the board row.
Persist each AI verdict against the change request identifier and the specific revision it reviewed. If the change request receives new edits after the review ran, mark the stored verdict as outdated in the interface so nobody merges on the strength of a review of older content. While the agent is running, show that state on the row and in the detail view so two reviewers do not kick it off twice.
A few rules to bake in. The app is a review surface, so it should never create change requests and never merge anything automatically; every merge is a deliberate human click. Handle spaces that have no open change requests gracefully rather than erroring, and keep the board usable when a space returns a lot of requests. The board itself is the thing my team lives in each morning, so it should load fast and make the overdue and stale items impossible to miss.
What does this prompt do?
- Pulls every open change request from all of your GitBook spaces into a single board showing the subject, who wrote it, which space it targets, how many days it has been waiting, and where it stands in review.
- Floats anything sitting longer than five days to the top, and flags edits whose underlying pages have changed since the request was opened, because those are the ones that merge badly.
- Opens each request next to the pages it changes and its full comment thread, so a reviewer can comment, approve, request changes, merge, or nudge the author in Slack right there.
- Adds a Review with AI button that reads the edit, checks it against the rest of your published docs for statements it now contradicts, posts what it finds as a comment, and shows its verdict in the app before anyone merges.
What do I need to use this?
- A GitBook account with access to the spaces your team edits
- Permission to review and merge change requests in those spaces
- A Slack workspace, only if you want the app to nudge authors about edits that are going stale
How can I customize it?
- Change the aging threshold. Five days is the default, but a fast moving docs team might want anything over two days flagged.
- Narrow the board to the handful of spaces your team actually owns instead of the whole organization.
- Send the Slack nudge to a shared docs channel instead of a direct message to the author.
- Tell the AI reviewer what matters most to you, whether that is contradictions with published pages, broken cross references, or terminology drift.
FAQs
Can I approve and merge edits without opening GitBook?
What does the stale badge mean?
Does the AI reviewer merge anything on its own?
Will this respect our approval rules?
Do I need Slack for this to work?
Related templates
Type in a candidate address and get a scorecard of nearby competitors, foot traffic anchors, and drive time from every site you already run.
Move every draft from Drive to your email list in one screen: pick the audience, see the real recipient count, and send without fixing formatting by hand.
One register for every piece of equipment and every software seat, with a dated record of who had what, so nothing depends on a shared spreadsheet again.
See which GitLab projects have the files and settings your team agreed on, and turn every gap into a merge request someone reviews.
One screen where sales, success, and marketing can search every call transcript by keyword, watch mention trends, and share AI summaries to Slack.
See every open merge request across your GitLab projects in one board, spot who is buried in reviews, and reassign, comment, nudge or merge right from the row.
Stop checking every GitBook space one at a time.
Open one board each morning, see every edit waiting on review, and clear the queue before anything goes stale.