mcpField
U
update-project

update-project

github.com/tartinerlabsDevelopment8378 installsUpdated 6d ago
Repository

About update-project

A development skill for keeping project documentation aligned with recent code changes and commits. It checks documentation against the repository and updates only claims that can be verified.

Key features

  1. 01Reviews recent commits and diffs
  2. 02Checks agent instruction files and README
  3. 03Scans agent, skill, and rule components
  4. 04Updates documentation based on project state
  5. 05Validates documented commands and setup

Use cases

  1. 01Refreshing docs after significant code changes
  2. 02Checking documentation before a release
  3. 03Finding stale agent instructions and component docs

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/tartinerlabs/skills --skill update-project

After installing, type/update-projectin Claude Code to confirm it loaded.

Bundled filesrules/agent-docs.mdrules/components.md

Details

From the project README

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.

AGENTS.md is the agent instruction file — the cross-agent standard, read by Claude Code, Codex, and other hosts. Treat CLAUDE.md as legacy: maintain one that exists, but do not create a new one. Component directories follow the same split — .claude/ for Claude Code, .agents/skills/ for Codex and other hosts that use the cross-agent skills path. Do not invent .agents/agents or .agents/rules.

Rules Overview

RuleImpactFile
Agent docs (AGENTS.md / CLAUDE.md / README.md)HIGHrules/agent-docs.md
Components (agents, skills, rules)MEDIUMrules/components.md

Workflow

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

  • rules/agent-docs.md for AGENTS.md / CLAUDE.md / README.md changes
  • rules/components.md for .claude/ agents, skills, and rules, and for .agents/skills/
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 (AGENTS.md), README.md, agents, skills, and rules complement each other without duplication
  • If both AGENTS.md and CLAUDE.md exist, propose consolidating into AGENTS.md per rules/agent-docs.md rather than keeping divergent copies

Comments

Markdown supported