Jesse A. Green / notebook

Live demo: the DocCompiler guide library as a static, read-only snapshot (October 2026). No backend, no accounts, nothing to submit.

Guide library

Unofficial, AI-generated user and admin guides for open-source repositories, from my DocCompiler proof of concept. Read-only.

Try it in two minutes

  1. Pick a project you already know

    Each repository page links the User Guide, the Admin Guide, the Markdown and the upstream commit the guide was written from. Compare it with the project's own docs.

  2. Or let the index pick one

    Opens a random repository page from all 514.

  3. Then look for three things

    • Provenance under the title: the month the guide was generated and the upstream commit it was written from.
    • The yellow notice: the library is checked by sampling, so the guide you opened was most likely not individually reviewed.
    • On this page: the section list beside each guide, for jumping between install, configuration and the rest.

What this is not: there is no job submission and there are no accounts, and nothing on this site calls a model. How the guides are produced is on the DocCompiler project page.

2What this is

These guides come from DocCompiler, a personal proof of concept. Claude Code agents wrote them, most of them between April and June 2026. Each repository has a User Guide, and most also have an Admin Guide.

The library is static and read-only. There are no accounts and nothing to submit.

3How the guides were made

A deterministic step builds a briefing for each repository from its source, with no LLM involved: entry points, config ground truth, a module index and real issues. Agents write the guides from that briefing under written rules: the briefing wins, never invent, and if extraction found nothing, don't write about it. Where the briefing fell short, the agents also read the cloned source, so not every statement traces back to the briefing.

4Read them with care

  • They are unofficial and AI-generated. They are not reviewed or endorsed by the projects they describe.
  • Accuracy is checked by sampling, one repository per review. Three repositories have been reviewed so far, so almost every guide here was not individually reviewed. The three reviews scored 49, 52 and 55 out of 70. The latest checked about 30 claims against upstream source and found 1 factual error, 1 evasive answer and 1 minor issue.
  • Fewer than 1 in 10 guides cite source files by line.
  • Each guide is a snapshot. Its footer gives the month it was generated and the repository and commit it was built from. Upstream may have moved on since.
  • Check a guide against the project's own docs before you rely on it.
  • Some repositories are not in this library.

6Private guides

Guides for the Palo Alto Networks open-source repositories, plus one custom playbook, are kept behind the portfolio's private password. The link below asks for it first.

Private Palo Alto Networks org (10 repositories + 1 playbook) Guides for the vendor's own open-source repositories, kept behind the private password.

7Browse by owner

0-9

A

B

C

D

E

F

G

H

I

J

K

L

M

N

O

P

Q

R

S

T

U

V

W

X

Y

Z