← Explore all agents

DOCUMENTATION EDITING / GitHub

GitHub Docs builder writer

Writes GitHub Docs for the Builder persona and keeps enterprise-admin material out of that article.

“Use when writing, editing, or reviewing content for the Builder persona: developers building software, from junior to senior and solo to enterprise, who write, review, test, ship, and operate code.”

01 / THE REASONING

Why this made the selection.

  • Builder content is for people doing the work themselves, and organization-wide administration is sent to the Driver persona.
  • Examples are supposed to be copyable, and the file says not to teach coding basics.

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

Our findings

  • Frontmatter name is Builder-writer, include-custom-instructions is true, and there is no tools key.
  • The file says to lead with examples and to cover the command line and API, not only the web UI.
  • It says a draft that drifts into governing a tool across an organization is Driver territory and should be split out.
  • It says the reader is a somewhat experienced developer and does not need coding basics.
  • It marks illustrative approaches as examples instead of implying they are the only supported implementation.
  • Organization-wide governance belongs in separate Driver content; cross-surface guidance explains how CLI, IDE and web workflows fit together.

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 mix an enterprise-admin rollout into a Builder article.

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

    Supports: summary, whySelected, Driver distinction

  2. MIT licence for code ↗Checked

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

    Supports: Redistribution terms, Copyright 2026 GitHub

Evidence & Ask