# Keep Docs Current

Detects docs drift after code changes and adds release notes without rewriting sections.

- Repository: https://github.com/paperclipai/paperclip (109885 stars)
- Category: Documents
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add paperclipai/paperclip --skill doc-maintenance -g -a claude-code -y`
Codex: `npx skills add paperclipai/paperclip --skill doc-maintenance -g -a codex -y`
Cursor: `npx skills add paperclipai/paperclip --skill doc-maintenance -g -a cursor -y`
Gemini CLI: `npx skills add paperclipai/paperclip --skill doc-maintenance -g -a gemini-cli -y`

## Description

Keep project docs aligned with recent code and feature changes, detect drift, update affected pages, and add release-relevant notes without rewriting unchanged sections.

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

# Doc Maintenance

Keep the documentation honest with minimum churn. The goal is alignment between docs and behavior, not stylistic rewrites or cosmetic re-organization. Reviewers should be able to read a diff and see "this updates docs to match recent behavior changes".

## When to use

- A PR or recent set of merges changed user-visible behavior: CLI flags, API shapes, default values, configuration keys, endpoints, environment variables, supported versions.
- A user-reported bug traced back to outdated documentation.
- A release is being cut and the docs need a pass against the merged commits.
- A new feature shipped but only the engineer's PR description describes how to use it.

## When not to use

- The change is internal-only (private helper rename, refactor) with no user-visible impact.
- You want to "improve the docs" without a behavior anchor. That is a separate scoped project, not maintenance, make a plan first.

## The pass

The rest: https://github.com/paperclipai/paperclip/blob/HEAD/packages/skills-catalog/catalog/bundled/docs/doc-maintenance/SKILL.md