DocuPilot — Claude-powered auto-documentation for GitHub repos

[AkrMcmr]

Built a tool that uses Claude to automatically keep your documentation in sync with code changes.

How it works

1. Push code to GitHub
2. DocuPilot analyzes the diff using Claude API
3. Generates/updates README, CHANGELOG, and API docs
4. Opens a PR for review (never pushes directly)

Two ways to use it

GitHub Action (bring your own API key):

- uses: AkrMcmr/docupilot-action@v1
  with:
    anthropic-api-key: ${{ secrets.ANTHROPIC_API_KEY }}

SaaS (zero config — install GitHub App and go):

• docupilot-alpha.vercel.app
• Free for 1 repo, $9/mo for 5 repos

Live demo — DocuPilot documents itself

• docupilot#2 — auto-generated README + CHANGELOG for its own codebase
• docupilot-action#1 — same for the action repo

Built with Next.js + Vercel + Claude API + Stripe. The Claude API integration was straightforward — structured prompts with the diff context produce surprisingly good documentation.

Would love feedback! GitHub | Action

[affaan-m]

The PR-based workflow is the right default. Documentation generators should propose diffs, not silently rewrite docs on main.

The review bar I would suggest for this category:

1. Least-privilege GitHub permissions for the Action/App.
2. API keys only through GitHub secrets or app-side secret storage, never repo files.
3. Clear maximum diff/context limits so large repos do not produce low-quality broad rewrites.
4. A way to distinguish generated docs from maintainer-authored docs.
5. A refusal path when code changes are too ambiguous to document safely.

For ECC users, the useful pattern is not just auto-docs; it is doc changes as reviewable artifacts with provenance. If DocuPilot keeps that boundary, it fits the same workflow discipline this repo tries to encourage.