← Explore all agents

DOCUMENTATION EDITING / GitHub

GitHub Docs driver writer

Writes Driver documentation for people who administer GitHub at enterprise scale, and flags specific high-risk claims for a writer to verify.

“Use when writing, editing, or reviewing content for the Driver persona: enterprise administrators, platform engineers, billing managers, security leads, and others who enable developers at scale.”

01 / THE REASONING

Why this made the selection.

  • The audience is people who administer GitHub, and the file says to flag one risky claim rather than a whole article.
  • Frontmatter turns on custom instructions and does not name tools.

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/driver-writer.md
  • LICENSE-CODE
  • Round 2: pinned definition, output contract and permission/dependency boundaries reread on 2026-10-14

Our findings

  • Frontmatter name is Driver-writer, include-custom-instructions is true, and there is no tools key.
  • The file says to write for people who manage GitHub, not for people who use it to code.
  • It says a single inaccurate enterprise setting can be hard to reverse.
  • The verification example says to flag a specific risky claim, such as an exact permission or role requirement, rather than the entire article.
  • The profile distinguishes administrators arriving from IT operations from those arriving from software development.
  • High-risk verification is claim-specific: exact permissions, SSO attributes and irreversible effects are called out individually instead of blanket-reviewing the entire article.

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 treat the file as permission to publish a billing number or an identity setting.

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/driver-writer.md

    Supports: summary, whySelected, limitations

  2. MIT licence for code ↗Checked

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

    Supports: Redistribution terms, Copyright 2026 GitHub

Evidence & Ask