---
name: Update Docs
slug: update-docs-2
category: Writing
description: Update Docs refreshes AGENTS.md files with patterns, commands, and conventions learned during a development session. Use it when new project knowledge should be recorded at the right scope.
github: "https://github.com/saffron-health/libretto/tree/main/.agents/skills/update-docs"
language: TypeScript
stars: 877
forks: 67
install: "npx degit https://github.com/saffron-health/libretto/tree/main/.agents/skills/update-docs ~/.claude/skills/update-docs"
installs_to: ~/.claude/skills/update-docs
source_path: .agents/skills/update-docs/SKILL.md
collection_size: 23
category_size: 1012
collection_url: "https://dirskills.com/collections/saffron-health/libretto"
added: 2026-08-22T05:21:22.561Z
last_synced: 2026-08-22T05:21:22.561Z
canonical_url: "https://dirskills.com/skills/update-docs-2"
---

# Update Docs

Update Docs refreshes AGENTS.md files with patterns, commands, and conventions learned during a development session. Use it when new project knowledge should be recorded at the right scope.

**Install:**

```bash
npx degit https://github.com/saffron-health/libretto/tree/main/.agents/skills/update-docs ~/.claude/skills/update-docs
```

## README

Update AGENTS.md files based on what was learned in this session about: $TOPIC

Read `./references/updating-agents-docs.md` for full guidelines before proceeding.

## Process

1. Review the conversation for learnings about the specified topic:
   - Patterns or conventions discovered
   - Commands needed but not documented
   - Architectural insights
   - Common pitfalls encountered

2. Determine where each learning belongs (lowest common ancestor):
   - Root `AGENTS.md` for repo-wide patterns
   - Package-level AGENTS.md for package-specific patterns
   - `docs/*.md` for detailed explanations

3. Check if the target AGENTS.md already has related content:
   - If multiple related items exist, consider extracting to a docs/ page
   - If adding would make the file too long (>60 lines for root), extract to docs/

4. Apply changes following the writing style in the guidelines

5. List what was updated and why