How do I install the Update Project skill?

Run npx skillmds add tartinerlabs/update-project in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Update Project safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Update Project?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Update Project free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Update Project?

tartinerlabs (@tartinerlabs) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Update Project by tartinerlabs — Agent Skill

Name: Update Project
Rating: 4.2 (5 reviews)
Author: tartinerlabs

File contents

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 and the cross-agent standard), or both. 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

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 .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 CLAUDE.md / AGENTS.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 (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

---name: update-projectdescription: 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.license: MIT--- 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 and the cross-agent standard), or both. 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 | 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 `.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 CLAUDE.md / AGENTS.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 (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

Frequently asked questions