Meet RepoWrit
Your code evolves every day. Your documentation shouldn't be stuck in the past.
RepoWrit is an AI-powered GitHub App that automatically generates and updates your project documentation every time you push code. No more stale READMEs. No more "I'll update the docs later." It just happens.
Why We Built This
We're developers. We love writing code. We do not love writing documentation.
Every team we've been on has the same story: the README was great on day one. Six months later, it describes a project that no longer exists. API endpoints have changed, setup instructions are wrong, and that "Architecture Overview" section is a fossil from three refactors ago.
This is Documentation Debt and just like tech debt, it compounds. New contributors get lost. Onboarding takes days instead of hours. Knowledge lives in Slack threads and the heads of senior engineers who are too busy to write it down.
We built RepoWrit because we believe documentation should keep up with code automatically. Not as an afterthought. Not as a Friday afternoon chore. As a living, breathing part of your development workflow.
How It Works
Step 1: Connect Your Repos
Install the RepoWrit GitHub App and select the repositories you want to keep documented. It takes about 30 seconds.
Step 2: Push Code Like Normal
Every time you push commits or merge a PR, RepoWrit's AI agent analyzes your changes. It doesn't just look at what changed, it understands why it changed using Claude by Anthropic.
Step 3: Get Updated Documentation
RepoWrit generates commit-aware summaries, executive briefings, and semantic search indexes for your codebase. Your documentation stays current without you lifting a finger.
More Than Just READMEs
Executive Summary — Your Codebase at a Glance
RepoWrit analyzes your recent commits and generates an AI-powered briefing with three perspectives:
- CTO View - Tech debt scoring, architectural drift detection, hardcoded secrets scanning, and consistency risk alerts (e.g., code changed but tests or docs weren't updated). See your codebase health as a single score from 0–100.
- PM View - Where is your team's energy going? RepoWrit breaks down effort into Features, Bugs, Refactoring, Docs, and Infrastructure with a visual energy distribution chart. It even calculates your Efficiency Multiplier - how many hours of documentation writing RepoWrit saved you, converted to dollars.
- Founder View - Knowledge moat percentage, documentation coverage, and exit readiness scores. Know how much of your codebase is proprietary competitive advantage vs. boilerplate.
No more "what did we ship this week?" Slack threads. Just open the Executive Summary.
Semantic Search — Ask Your Codebase Anything
Every commit RepoWrit processes is embedded into a searchable knowledge graph. Instead of grepping through git logs, just ask in plain English:
- "What security changes were made last month?"
- "Which repos are still using localStorage?"
- "Show me breaking changes that removed backwards compatibility"
- "Who worked on authentication recently?"
Results are ranked by relevance with similarity scores, impact badges, and developer attribution. It's like having a senior engineer who remembers every commit across every repo.
Our Philosophy
- Documentation should be alive. Static docs are dead docs. RepoWrit regenerates documentation with every meaningful change.
- AI should understand intent, not just diffs. We use Claude to analyze the purpose behind code changes, not just the lines that moved.
- Privacy is non-negotiable. We don't store your source code long-term. We don't train models on your data. Your code is yours. Period.
Privacy First
We take your trust seriously:
- No code storage - Your source code is processed in-memory and never stored on our servers long-term.
- No model training - Your code is never used to train AI models. We use Anthropic's API with zero-retention settings.
- Minimal permissions - We only request the GitHub App permissions we need, and only access your code when a sync is triggered.
- You're in control - Disconnect your repos at any time and your data is removed.
Built by developers, for developers. Because your code deserves documentation that keeps up.