DocForge AI — release docs from your git history

DocForge turns your commits into the documents your team actually needs — release notes, QA checklists, executable test cases with test data, and UAT/deployment handover docs — as Markdown, Word (.docx), and Excel (.xlsx).

Everything runs on your machine. Your code is analyzed locally (git diff + tree-sitter AST); only the prompts you approve are sent to the AI provider you configure with your own API key.

Quick start

Open any git repository.
Run DocForge: Set AI Provider API Key — pick Claude, Gemini, or OpenAI and paste your key (stored in your OS keychain, never in settings files).
Run DocForge: Generate Release Notes — accept the defaults (HEAD~1 → HEAD) and watch the release notes open.
For the full pack, run DocForge: Generate Handover Pack — pick any of Release Notes, QA Checklist, Test Cases + Test Data, and Deployment/UAT Handover. Files land in a .docforge/ folder in your repo.

Commands

Command	What it does
`DocForge: Generate Release Notes`	Release notes for a commit range (md + json)
`DocForge: Generate Handover Pack`	Any combination of the four document types as .docx/.xlsx/.json
`DocForge: Set AI Provider API Key`	Store your Claude/Gemini/OpenAI key securely
`DocForge: Set Cloud Access Token`	Store a DocForge dashboard token (optional sync)
`DocForge: Sync Documents to Cloud`	Upload generated documents to your team dashboard — always behind an explicit consent dialog

Your templates, filled automatically

Drop your company's own Word/Excel templates into .docforge/templates/ (e.g. test-cases.xlsx with your column headers, or release-notes.docx with {{placeholders}}) and DocForge fills your format instead of its built-in one. Recognized names: release-notes.docx, qa-checklist.docx, test-cases.docx, test-cases.xlsx, deployment-handover.docx.

Settings

Setting	Default	Purpose
`docforge.provider`	`claude`	AI provider: `claude`, `gemini`, or `openai`
`docforge.model`	(provider default)	Optional model override
`docforge.cloud.baseUrl`	(empty = fully local)	Your DocForge dashboard URL
`docforge.cloud.organizationId`	—	Organization to sync into
`docforge.cloud.projectName`	(folder name)	Project name used when syncing

Privacy, in plain words

Read-only git: DocForge never commits, never installs hooks, never modifies your repository. Its only write is the .docforge/ output folder.
Local analysis: diffs and code structure are computed on your machine.
BYOK: code snippets are sent only to the AI provider you configured, under your own API key. No DocForge servers see your code.
Opt-in sync: cloud sync is off until you configure it, and every upload shows a consent dialog listing exactly what will be sent — generated documents only, never source code.

Requirements

git available on your PATH
An API key for Claude, Gemini, or OpenAI
Works with any git hosting (GitHub, GitLab, Bitbucket, self-hosted — or none)