update-claude-md

Update CLAUDE.md files with new decisions and conventions from conversations.

23|2|Updated Mar 1, 2026
One-click install
npx skills add https://github.com/tta-lab/ttal-cli --skill update-claude-md-tta-lab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: update-claude-md
Source: https://github.com/tta-lab/ttal-cli/tree/main/skills/update-claude-md
Command: npx skills add https://github.com/tta-lab/ttal-cli --skill update-claude-md-tta-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents important decisions and conventions from being lost between conversations, so future agents can act with the same context and preferences.

Core Features & Use Cases

  • Find and update the correct CLAUDE.md: Updates the agent-owned CLAUDE.md under ~/clawd/ or the project-root CLAUDE.md for other repos.
  • Capture only what is new: Reads the current file, avoids duplication, and adds concise instruction-style guidance in the right existing section.
  • Preserve long-term signal: Focuses on workflow decisions, conventions, tool preferences, gotchas, and architecture choices while excluding session-specific or speculative details.

Quick Start

After a meaningful conversation, ask the assistant to update the repository’s CLAUDE.md with only the new decisions and conventions that should persist into future sessions.

Frequently Asked Questions about update-claude-md

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

FAQPage Schema
How do I save Claude agent instructions and conventions to a project for future sessions?▼

You can persist agent instructions by updating the CLAUDE.md file in your project root or ~/clawd/ workspace. This captures workflow decisions and conventions so future agent sessions retain the same operational context.

What is the best way to keep CLAUDE.md updated with only new repo context?▼

The best way to keep CLAUDE.md updated is to read the existing file first to avoid duplication. You then insert concise, instruction-style updates into matching sections, focusing only on new decisions and excluding speculative details.

When do I need to update the CLAUDE.md file for my repository?▼

You need to update CLAUDE.md after a meaningful conversation where key decisions, gotchas, or conventions were established. This ensures actionable knowledge is captured for future agent sessions rather than being lost.

Does updating CLAUDE.md capture session-specific chat history?▼

No, updating CLAUDE.md does not capture session-specific or speculative information. It strictly preserves long-term signal such as workflow decisions, tool preferences, and architecture choices to guide future agent sessions.

How do I avoid duplicate agent instructions when updating CLAUDE.md?▼

To avoid duplicate agent instructions, read the existing CLAUDE.md content before making changes. This allows you to identify what is already documented and insert only concise instruction-style updates into the appropriate matching sections.