# Update Docs

Update documentation pages to match source code changes on the current branch

- Repository: https://github.com/pipecat-ai/pipecat (16982 stars)
- Category: Writing
- License: BSD-2-Clause
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add pipecat-ai/pipecat --skill update-docs -g -a claude-code -y`
Codex: `npx skills add pipecat-ai/pipecat --skill update-docs -g -a codex -y`
Cursor: `npx skills add pipecat-ai/pipecat --skill update-docs -g -a cursor -y`
Gemini CLI: `npx skills add pipecat-ai/pipecat --skill update-docs -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add pipecat-ai/pipecat`

## Description

Update documentation pages to match source code changes on the current branch

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

Update documentation pages to reflect source code changes on the current branch. Analyzes the diff against main, maps changed source files to their corresponding doc pages, and makes targeted edits.

This skill is repo-agnostic and shared. It is published by the
`pipecat-dev-skills` marketplace and used by every repository whose changes feed
`pipecat-ai/docs`, so it must stay free of anything specific to one of them.

Everything repo-specific, what is in scope, how files map to pages, what a new
page looks like, where it gets registered, comes from that repo's **profile**,
`.claude/skills/update-docs/SOURCE_DOC_MAPPING.md`, which lives in the repo
being documented. The skill never hardcodes a source path, a page template, or a
navigation group. See `PROFILE_CONTRACT.md` for what a profile must provide.

How pages read, what to document, what to leave out, page templates, prose, comes from the docs repo's style guide, `DOCS_PATH/STYLE.md`. This skill covers
the process: finding what changed, deciding what the docs need, and checking
the result.

`REVIEW.md` is a second pass over a finished update, run in a fresh session
that did not write it. The automation runs it after this skill; run it by hand
the same way after a local update.

## Arguments

```
/update-docs [DOCS_PATH]
```

- `DOCS_PATH` (optional): Path to the docs repository root. If not provided, ask the user.

Examples:

- `/update-docs /Users/me/src/docs`
- `/update-docs`

## Instructions

### Step 1: Resolve docs path, profile, and style guide

If `DOCS_PATH` was provided as an argument, use it. Otherwise, ask the user for the path to their docs repository.

Verify the path exists and contains `docs.json`.

The rest: https://github.com/pipecat-ai/pipecat/blob/HEAD/.claude/skills/update-docs/SKILL.md