are-update
Keeps project documentation in sync with codebase changes by running incremental updates.
Install
mkdir -p .claude/skills/are-update && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/11976" && unzip -o skill.zip -d .claude/skills/are-update && rm skill.zipInstalls to .claude/skills/are-update
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Incrementally update documentation for changed filesKey capabilities
- →Read the current version of agents-reverse-engineer
- →Run the update command in the background
- →Monitor progress by polling log files
- →Summarize updated, unchanged, and orphaned files
- →Include staged but uncommitted changes with `--uncommitted`
- →Show what would be updated without writing with `--dry-run`
How it works
The skill reads the current version of agents-reverse-engineer, runs the update command in the background, and monitors its progress by polling log files until completion, then summarizes the changes.
Inputs & outputs
When to use are-update
- →Updating docs after a feature merge
- →Running documentation sync in a CI pipeline
- →Identifying orphaned documentation
About this skill
Update documentation for files that changed since last run.
<execution> Run the update command in the background and monitor progress in real time.Steps
-
Read version: Read
.claude/ARE-VERSION→ store as$VERSION. Show the user:agents-reverse-engineer v$VERSION -
Run the update command in the background using
run_in_background: true:npx agents-reverse-engineer@$VERSION update --backend claude $ARGUMENTS -
Monitor progress by polling the latest progress log:
- Wait ~15 seconds (use
sleep 15in Bash), then use Glob to find the latest.agents-reverse-engineer/progress-*.logfile, and Read it (use theoffsetparameter to read only the last ~20 lines for long files) - Show the user a brief progress update (e.g. "12/30 files updated, ~5m remaining")
- Check whether the background task has completed using
TaskOutputwithblock: false - Repeat until the background task finishes
- Important: Keep polling even if no progress log exists yet (the command takes a few seconds to start writing)
- Wait ~15 seconds (use
-
On completion, read the full background task output and summarize:
- Files updated
- Files unchanged
- Any orphaned docs cleaned up
Options:
--uncommitted: Include staged but uncommitted changes--dry-run: Show what would be updated without writing--eval: Namespace output by backend.model for side-by-side comparison--concurrency N: Control number of parallel AI calls (default: auto)--fail-fast: Stop on first file analysis failure--debug: Show AI prompts and backend details--trace: Enable concurrency tracing to.agents-reverse-engineer/traces/
When not to use it
- →When a full, non-incremental documentation update is desired
- →When real-time progress monitoring is not needed
- →When the update command should not run in the background
Limitations
- →Requires `npx agents-reverse-engineer` to be available
- →Progress monitoring relies on polling log files
- →Output is summarized after background task completion
How it compares
This skill incrementally updates documentation for changed files in the background with real-time progress monitoring, unlike a manual or full documentation regeneration.
Compared to similar skills
are-update side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| are-update (this skill) | 0 | 5mo | Review | Intermediate |
| architecture-decision-records | 54 | 5mo | Review | Beginner |
| meeting-minutes | 41 | 6mo | No flags | Beginner |
| docs-write | 22 | 6mo | No flags | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
architecture-decision-records
wshobson
Write and maintain Architecture Decision Records (ADRs) following best practices for technical decision documentation. Use when documenting significant technical decisions, reviewing past architectural choices, or establishing decision processes.
meeting-minutes
github
Generate concise, actionable meeting minutes for internal meetings. Includes metadata, attendees, agenda, decisions, action items (owner + due date), and follow-up steps.
docs-write
metabase
Write documentation following Metabase's conversational, clear, and user-focused style. Use when creating or editing documentation files (markdown, MDX, etc.).
rust-docs-guidelines
RediSearch
Guidelines for writing Rust documentation
ml-paper-writing
davila7
Write publication-ready ML/AI papers for NeurIPS, ICML, ICLR, ACL, AAAI, COLM. Use when drafting papers from research repos, structuring arguments, verifying citations, or preparing camera-ready submissions. Includes LaTeX templates, reviewer guidelines, and citation verification workflows.
content-research-writer
ComposioHQ
Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section. Transforms your writing process from solo effort to collaborative partnership.