update-project

Synchronize CLAUDE.md and related docs with current code changes.

7|1|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/tartinerlabs/skills --skill update-project-tartinerlabs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-project
Source: https://github.com/tartinerlabs/skills/tree/main/skills/update-project
Command: npx skills add https://github.com/tartinerlabs/skills --skill update-project-tartinerlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps project documentation aligned with code changes by updating CLAUDE.md and related docs to reflect current state.

Core Features & Use Cases

  • Detects stale CLAUDE.md, README.md, and rules sections by comparing against the latest codebase.
  • Updates CLAUDE.md, README.md, and related docs using rule cues from rules/ to maintain consistency.
  • Validates updates after changes to ensure documentation accuracy before release or deployment.

Quick Start

Run after significant code changes to sync CLAUDE.md and related docs with the latest project state.

Frequently Asked Questions about update-project

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I keep CLAUDE.md and README documentation in sync with code changes?

To keep CLAUDE.md and README documentation in sync with code changes, you can run a documentation synchronization workflow that detects stale sections and updates project docs to reflect the current codebase state.

What is the best way to update project documentation before a release?

The best way to update project documentation before a release is to run a validation workflow that reads rule files under the rules/ directory to guide updates and ensure documentation accuracy across CLAUDE.md and README files.

Can I use rule files to guide README and CLAUDE.md updates?

Yes, you can use rule files to guide README and CLAUDE.md updates. The synchronization process reads rule cues from the rules/ directory to maintain consistency and validate updates against the latest codebase.

When should I run a documentation synchronization workflow?

You should run a documentation synchronization workflow after significant code changes or before releases. This ensures your CLAUDE.md, README.md, and related docs accurately reflect the latest project state before deployment.

Does updating project documentation require complex setup or dependencies?

Updating project documentation requires no complex setup or dependencies. It uses a deterministic workflow with low effort that is compatible with the sonnet model, needing only existing rule files to guide the synchronization.