Update project

Skill tartinerlabs/skills/skills/update-project

Use when updating docs, syncing CLAUDE.md, AGENTS.md, or README.md, fixing stale documentation, or refreshing project rules and skills. Keeps docs aligned with code changes.From its SKILL.md

Install

npx -y skills add tartinerlabs/skills --skill update-project

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

7 stars7 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
runs commandsInstructs the agent to run 2 commands, including `git log --oneline -20` and 1 more.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.4 KB, 466 tokens by cl100k_base, as published. Nobody here has run it

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.

Update only what the project actually changed. Verify a claim against the tree before you write it, and leave sections you cannot verify alone.

Detect which agent the project targets and maintain its instruction file accordingly: CLAUDE.md (Claude Code), AGENTS.md (Codex, OpenCode, and the cross-agent standard), or both. Component directories follow the same split — .claude/ for Claude Code, .agents/ for the cross-agent convention.

Rules Overview

Rule	Impact	File
Agent docs (CLAUDE.md / AGENTS.md / README.md)	HIGH	`rules/agent-docs.md`
Components (agents, skills, rules)	MEDIUM	`rules/components.md`

Workflow

Step 1: Detect

Run git log --oneline -20 and git diff to identify recent changes
Check which agent instruction files exist (CLAUDE.md, AGENTS.md) and whether README.md exists (create if missing)
Scan both .claude/ and .agents/ for agents/*.md, skills/*/SKILL.md, and rules/*.md files
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 and apply updates:

rules/agent-docs.md for CLAUDE.md / AGENTS.md / README.md changes
rules/components.md for .claude/ or .agents/ agents, skills, and rules changes

Step 3: Validate

Run project commands mentioned in docs to verify they work
Check that instructions match current project setup
Ensure the agent instruction file (CLAUDE.md / AGENTS.md), README.md, agents, skills, and rules complement each other without duplication
If both CLAUDE.md and AGENTS.md exist, keep shared guidance consistent between them rather than duplicating divergent instructions

What ships with it: 2 files

4.9 KB alongside SKILL.md

rules/

agent-docs.md2.1 KB
components.md2.9 KB

Gives 0 of the 12 instructions most docs writing skills give in 466 tokens

Counted across 1,951 of the 3,904 authors here whose files we hold, read 2026-09-06

Use third-person for skill descriptionsin 54 of 1951, across 35 files
Start descriptions with Use whenin 43 of 1951, across 29 files
Run baseline scenarios before writing any skillin 40 of 1951, across 26 files
Use active voicein 40 of 1951, across 36 files
Map file responsibilities before defining tasksin 36 of 1951, across 29 files
Use checkbox syntax for tracking stepsin 35 of 1951, across 27 files
Ask one question at a timein 35 of 1951
Offer execution options after saving the planin 33 of 1951, across 24 files
Include complete code in every stepin 33 of 1951, across 27 files
Design units with clear boundaries and interfacesin 31 of 1951, across 23 files
Announce the skill usage at the startin 30 of 1951
Verify agent compliance after adding the skillin 29 of 1951, across 17 files

Said here and by no other author read

Verify claims against the file tree before writing
Update only what the project actually changed
Ensure instructions match current project setup
Keep shared guidance consistent across instruction files

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.