co-maintainer
Review the change.
Know the codebase.
co-maintainer turns your code, pull requests, and commit history into repository-specific guides. Every review starts with that context, whether it runs on your laptop or on your server.
npm install -g co-maintainer
Built once. Available at review time.
Reads from the repository
Current source, structure, and workflows
Decisions, diffs, and review discussions
How the default branch changed over time
Writes repository-specific guides
SKILL.md
CODEBASE.md
PR_REVIEW_GUIDE.md
How it works
Context is built before review begins.
Not a prompt pasted onto a diff. co-maintainer first learns the repository and keeps that knowledge available for later reviews.
-
01
probeSamples the repository and gives you a bounded
initcommand. -
02
init/remakeBuilds and refreshes evidence-backed guides from code and project history.
-
03
reviewReviews a local diff or GitHub pull request against those guides.
One review, three paths
Use the context where your team needs it.
Local review
Your working tree, your local guides, your OpenRouter account.
co-maintainer review
02
PR review
Review an open GitHub pull request by number through gh.
co-maintainer review owner/repo 123
03
Shared context
Initialize once on serve. Developers review without rebuilding guides.
co-maintainer review --remote
Self-hosted
One server for context, reviews, and operations.
serve runs the dashboard, GitHub App webhooks, background jobs, and the remote review API. Your repository context stays under your control.
Start with one repository.
Install the CLI, run probe, and follow the command it gives you.