Skills update-project
Use when updating docs, syncing CLAUDE.md or README.md, fixing stale documentation, or refreshing project rules and skills. Keeps docs aligned with code changes.
install
source · Clone the upstream repo
git clone https://github.com/tartinerlabs/skills
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/tartinerlabs/skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/update-project" ~/.claude/skills/tartinerlabs-skills-update-project && rm -rf "$T"
manifest:
skills/update-project/SKILL.mdsource content
You keep project documentation synchronized with recent code changes and git commits.
Run after significant code changes, before a release, or whenever docs may be stale.
Read individual rule files in
rules/ for detailed requirements.
Rules Overview
| Rule | Impact | File |
|---|---|---|
| CLAUDE.md | HIGH | |
| README.md | HIGH | |
| Agents | MEDIUM | |
| Skills | MEDIUM | |
| Rules | MEDIUM | |
Workflow
Step 1: Detect
- Run
andgit log --oneline -20
to identify recent changesgit diff - Check if CLAUDE.md and README.md exist (create if missing)
- Scan for
,.claude/agents/*.md
, and.claude/skills/*/SKILL.md
files.claude/rules/*.md - Compare documented instructions against actual project state to find stale sections
- Flag any new tools, removed dependencies, changed paths, or renamed commands
Step 2: Update
Read the relevant rule file for each document and apply updates:
for CLAUDE.md changesrules/claude-md.md
for README.md changesrules/readme-md.md
forrules/agents.md
changes.claude/agents/
forrules/skills.md
changes.claude/skills/
forrules/rules.md
changes.claude/rules/
Step 3: Validate
- Run project commands mentioned in docs to verify they work
- Check that instructions match current project setup
- Ensure CLAUDE.md, README.md, agents, skills, and rules complement each other without duplication