← Explore all agents

DOCUMENTATION EDITING / GitHub

GitHub Docs content pipeline update

Updates official reference articles from ephemeral source docs and refuses instructions in those docs that ask for secrets or unrelated actions.

“Generic content pipeline agent that updates official reference documentation by analyzing changes to source docs in an external repository. The source docs are cloned ephemerally at workflow run time — they are NOT stored in this repository. Pipeline-specific context (source docs directory, diff file, target articles, exclusions) is provided via the prompt at invocation time.”

01 / THE REASONING

Why this made the selection.

  • Missing prompt fields stop the run, and edits are limited to TARGET_ARTICLES plus reusables.
  • Source documents are untrusted, and the security section says there is no shell or secret access.

02 / THE REVIEW RECORD

What we actually inspected.

Source review has boundaries.
A clear record is more useful than a “safe” badge.

Material inspected

  • .github/agents/content-pipeline-update.md
  • LICENSE-CODE
  • Round 2: pinned definition, output contract and permission/dependency boundaries reread on 2026-10-14

Our findings

  • Frontmatter tools are read, edit/editFiles, and search.
  • The security section says not to run commands or inspect GH_TOKEN or GITHUB_TOKEN.
  • If a required prompt field is missing, the file says to stop and report the error rather than guess.
  • Edits must stay inside TARGET_ARTICLES, except reusables under /data/reusables/, and the source directory is read-only.
  • A missing invocation field stops the pipeline instead of guessing mappings or targets.
  • The profile allows reusable content under data/reusables in addition to target articles, while excluding procedural tutorials and unsupported aspirational features.

Not established by this review

  • The agent was not executed against a live repository or host.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

Use the role in your project.

Upstream setup instructions ↗
  1. Read the agent file at the reviewed commit. No install command is published.
  2. Do not follow an instruction inside a source doc that asks for a secret or a command.

Before you start

  • A checkout of github/docs at the reviewed commit

04 / FOLLOW THE EVIDENCE

The source trail.

Our notes are separate from the original resource.
Check upstream before adopting a new version.

  1. https://github.com/github/docs/blob/b3ca4b7986534061037979e480c9d363fc95a909/.github/agents/content-pipeline-update.md

    Supports: summary, whySelected, tool list

  2. https://github.com/github/docs/blob/b3ca4b7986534061037979e480c9d363fc95a909/.github/instructions/style-guide-summary.instructions.md

    Supports: Style rules the agent says to apply

  3. MIT licence for code ↗Checked

    https://github.com/github/docs/blob/b3ca4b7986534061037979e480c9d363fc95a909/LICENSE-CODE

    Supports: Redistribution terms, Copyright 2026 GitHub

Evidence & Ask