RepoPlaybook
Now in early access

Turn Every Repo Into Living Documentation

RepoPlaybook automatically updates your docs from pull requests, code changes, and team workflows — so engineers always have the truth.

app.repoplaybook.com / acme-corp
PR #482 merged — auth service
Docs synced

AI summary

Introduced scoped API keys, rotated signing secrets, updated the public OpenAPI spec. On-call runbook reflects new validation middleware path.

Knowledge graph

authmiddlewareopenapirunbooksedge
docs/services/auth.mdjust now

Trusted by engineers at

VercelLinearRailwayPlanetscaleSupabaseLoomRetoolDescript

80%

fewer repeated questions

3×

faster new-hire onboarding

< 5 min

docs updated after every merge

Auto-updated documentation

Your docs update on every merge. No tickets. No reminders.

RepoPlaybook reads every diff like a senior engineer would — understanding intent, not just syntax — then rewrites the affected documentation before your PR branch is cold.

  • Updates runbooks, API docs, and architecture notes automatically
  • Shows a human-readable diff of what changed and why
  • Works across GitHub, GitLab, and Bitbucket
docs / services / auth.md — RepoPlaybook

PR #482 · diff

- Auth validates using JWT_SECRET
- Expiry hardcoded to 3600s
+ Scoped API keys with HMAC-256
+ Configurable TTL via env vars
+ Key rotation endpoint added
middleware/validate.ts
+ validateScope() guard
+ Rate-limit per key tier

auth.md

AI updated

# Auth Service

Uses scoped API keys with HMAC-256. TTL is configurable via AUTH_TOKEN_TTL.

Keys are rotated via POST /auth/rotate. See the runbook for incident playbook.

Scope validation
Per-key rate limits
Key rotation endpoint

PR summaries

AI-written PR briefs your whole team will actually read.

Forget wall-of-text changelogs. RepoPlaybook produces concise, opinionated summaries — risk level, rollout impact, rollback path — attached directly where the review happens.

  • Surfaces blast radius, not just file counts
  • Flags docs that need human review
  • One-click export to Slack, Notion, or Linear
github.com / acme / platform / pull / 482

Rate limiter hardening

by @priya · 12 files · +394 −87

Merged
edge/rate-limit.ts+142-23
redis/cache.ts+68-14
middleware/validate.ts+55-31
docs/edge/rate-limits.md+89-0
AI Summary

Hardens per-tenant burst limits with Redis-backed counters. Updates on-call checklist. No schema migrations.

Impact

Edge SLO preserved
No downtime risk
Rollback: feature flag

Docs updated

docs/edge/rate-limits.md

Ask your codebase AI

Every answer backed by the code your team actually ships.

Not a generic chatbot. RepoPlaybook grounds every response in your real diffs, files, and decisions — with citations you can click through to verify. When it doesn't know, it says so.

  • Answers come with source citations you can verify
  • Understands ownership, architecture, and history
  • Reduces repeated questions to your senior engineers
AI Copilot — acme-platform
U
How do we handle auth token expiry in the payment service?
AI
The payment service delegates to the shared auth middleware. Tokens expire after the value set in AUTH_TOKEN_TTL (default 3600s). Rotation is handled via POST /auth/rotate — see the runbook updated in PR #482.
docs/services/auth.mdrunbooks/key-rotation.md
U
Who owns the auth service?
AI
The Platform Security team (lead: @priya). Last updated 4 hours ago.
CODEOWNERS
Ask anything about your codebase…

Ownership mapping

Know who owns what, across every service, always.

As your org grows, tribal ownership becomes a liability. RepoPlaybook keeps a live map of every service, its owning team, doc freshness, and last known contributor — updated automatically.

  • Ownership synced from CODEOWNERS and Git history
  • Doc freshness score surfaces stale knowledge before incidents
  • Instant escalation paths for on-call engineers
Ownership Map — acme-platform
ServiceTeamReposDocs ageStatus
auth-servicePlatform Security34h ago
payment-gatewayPayments Core51d ago
notification-svcGrowth Eng23d ago
data-pipelineData Platform812h ago
api-gatewayPlatform Infra46h ago
5 services · 22 repos · median freshness 6hAll healthy

From the teams using it

“

New hires hit their first commit with context that used to take weeks to absorb. We cut repeated architecture questions by more than half.

EV

Elena Vasquez

CTO · Series B infra startup

“

The PR briefs catch edge cases our checklist missed. It feels like a staff engineer is quietly updating the wiki after every merge.

MC

Marcus Chen

Principal Engineer · Payments platform

“

We outgrew Notion as a source of truth. RepoPlaybook is the first tool that actually respects how we build software.

AO

Amira Okonkwo

Founder & CEO · Developer tools startup

Pricing

Transparent plans. No seat taxes. No surprises.

Starts at $49/month · ₹2,999/month for Indian teams. 14-day free trial on every plan.

Starter

$49/mo

₹2,999/mo in India

Small teams

Popular

Team

$199/mo

₹9,999/mo in India

Growing orgs

Growth

$499/mo

₹24,999/mo in India

Larger teams

EnterpriseSelf-hosted · SAML SSO · Custom SLA · Dedicated support
Talk to sales
  • 14-day free trial, no card needed
  • Cancel or change plans anytime
  • Annual billing saves 20%
  • Auto-detected regional pricing
See full plan comparison

FAQ

Answers for security, platform, and accuracy reviews — the ones that actually gate your purchase.

RepoPlaybook is designed for production engineering: least-privilege access to repositories, encryption in transit and at rest, optional customer-managed keys, and strict data residency options on Scale. We never train foundation models on your private code without an explicit, separate agreement.

Your docs should update themselves.

Join 200+ engineering teams who stopped fighting stale knowledge and started shipping with confidence.

No credit card · 14-day free trial · Cancel anytime