Every developer I know has the same problem.
The README describes a project from 6 months ago. The changelog
is either empty or a list of git hashes nobody can read. New
engineers spend their first two weeks asking questions that should
be answered by documentation.
Nobody fixes it because nobody has time.
I got tired of this and built Pushpen.
What it does
Pushpen connects to your GitHub repository via webhook. Every time
you push code, it:
- Reads the diff across all commits in the push
- Understands what actually changed — not just commit messages
- Generates updated documentation
- Opens a pull request for you to review and merge
The documentation it generates:
- README — kept accurate to your actual codebase
- Changelog — written in plain English from your diff
- API docs — updated when endpoints change
- Onboarding guide — so new team members can actually follow it
Why a PR and not a direct commit
I made a deliberate choice here. Pushpen never writes directly
to your codebase. Every update comes as a pull request.
You review it. You approve it. You merge it. Or you ignore it.
No surprises. No AI touching production directly.
What else it does
Beyond documentation, Pushpen also:
- Summarizes every PR with impact analysis and risk assessment
- Triages new GitHub issues automatically
- Analyzes CI failures and suggests fixes
- Tracks your repository health score over time
The tech stack
Built with Next.js 14, Supabase, Clerk, and Claude API via
OpenRouter. GitHub webhooks handle the event pipeline.
Try it free
Free plan — no credit card required.
Would love feedback from the dev.to community.
What would make you actually use something like this?
Top comments (0)