Update docs - Tembo Docs

Tembo monitors your codebase for changes and automatically updates your documentation repo to keep features well-documented.

How it works

Code changes detected

A PR is merged or code is pushed to your main branch. Tembo detects the change via webhook.

Docs analyzed

The agent compares the code changes against your existing documentation to identify gaps, outdated sections, or missing pages.

Docs updated

A PR is opened in your docs repo with updated content that reflects the code changes.

Set up a docs agent

On PR merge

Trigger: PR merged to main MCP Servers: GitHub

When a PR is merged:
Analyze the changes for user-facing impact
Check if existing docs cover the changed functionality
If docs are outdated or missing, open a PR in the docs repo with updates
Match the existing docs style and formatting

Weekly docs review

Trigger: Weekly MCP Servers: GitHub, Notion, Slack

Compare the codebase against the docs repo:
Find new features or API changes that aren't documented
Identify docs pages that reference removed or renamed functionality
Open a PR with updates for the most impactful gaps
Post a summary to #engineering in Slack

Best practices

Use a separate docs repo: Tembo can open PRs across repositories, so keep docs in their own repo for clean separation.
Add rule files: Include a rule file in your docs repo with style guidelines, formatting conventions, and tone.
Start with API docs: API documentation is the easiest to keep in sync since changes are mechanical and well-scoped.

⌘I

​How it works

​Set up a docs agent

​On PR merge

​Weekly docs review

​Best practices

How it works

Set up a docs agent

On PR merge

Weekly docs review

Best practices