Skip to content
DraftStack

How DraftStack works

Pipeline

Section titled “Pipeline”

A merged pull request starts the pipeline for each matching project.

  1. DraftStack receives the GitHub webhook and identifies the monitored repository.

  2. DraftStack fetches the diff, pull request title, description, comments, and reviews.

  3. DraftStack builds docs context from the manifest, matched pages, project knowledge, and configured style guides.

  4. DraftStack asks the model to plan the smallest safe docs update.

  5. DraftStack asks the model to write candidate file changes from the plan, source diff, existing docs, and style guide requirements.

  6. DraftStack reviews the candidate output for preservation, hallucinations, and blocking issues.

  7. DraftStack stores a suggestion with the diff, affected files, confidence, and reasoning summary.

  8. Approval creates a branch and draft GitHub pull request in the documentation repository.

DraftStack keeps non-target sections unchanged when it edits an existing page. That constraint prevents broad rewrites when a pull request only changes one endpoint, flag, or setup step.