Developer reference
Setup, architecture, APIs, extension points, configuration, and testing in docs/DEVELOPER.md.
Standalone documentation automation
Vendor one GitHub Action into a repository and continuously generate a developer reference, an end-user guide, and a NotebookLM-ready source.
What it produces
Docforge inspects the repository context you select and writes predictable Markdown artifacts back to the project.
Setup, architecture, APIs, extension points, configuration, and testing in docs/DEVELOPER.md.
Features, task-oriented instructions, examples, and troubleshooting in docs/USER_GUIDE.md.
A combined, attributed source in docs/NOTEBOOKLM.md, with optional direct upload.
Quick install
The installer adds Docforge as vendor/docforge, creates configuration, and installs the workflow.
curl -fsSL https://raw.githubusercontent.com/nikolareljin/docforge/main/install.sh | bash
# review generated configuration before committing
git diff -- .gitmodules .docforge.yml .github/workflows/docs.ymlReview remote scripts before piping them to a shell. The manual submodule installation provides the same result step by step.
Provider choice
The default GitHub Models provider uses the workflow token. Other providers use their own secret or local endpoint.
GitHub Models receives GITHUB_TOKEN automatically from the Actions runner.
Use Groq, Anthropic, Together, OpenRouter, Bedrock, or an OpenAI-compatible endpoint.
Choose Ollama for local runs where repository context must stay on your machine.
Related tools
Docforge is standalone automation—not a Claude Code plugin. Claude Docsmith provides an interactive, screenshot-aware documentation workflow inside Claude Code.
Plan or write separate user and developer documentation with interactive review and optional local tooling.
Explore Docsmith →Browse security, documentation, and media plugins through one marketplace.
Visit the plugin suite →Configuration, Docker, multi-repository setup, NotebookLM, and internals live with the source.
Browse documentation →