Skill

update-claude-md

Updates CLAUDE.md with workflow decisions, tool preferences, conventions, and patterns from recent conversations. Ensures context persists across sessions.

Markdown

Git

documentation

npx claudepluginhub tta-lab/ttal-cli --plugin ttal

Tool Access

This skill uses the workspace's default tool permissions.

Preview

After a meaningful conversation — decisions made, patterns discovered, preferences stated — the user may ask you to capture what was discussed into the project's CLAUDE.md. This ensures future sessions benefit from today's context.

SKILL.md

Similar Skills

claude-md-maintenance

Guides effective maintenance of CLAUDE.md files: adding lessons learned, updating conventions, restructuring instructions. Covers when to update/remove rules, structure templates, hierarchy, and size limits.

3 files

claude-workflow

grimoire

307

Updates CLAUDE.md knowledge library files across projects with new APIs, DB tables, pages, architecture, env vars, and dependencies. Activates on 'update context', 'update claude', or project changes.

memstack

learn

263

Extracts reusable strategic knowledge from session history (architecture, patterns, ops) and updates local CLAUDE.md. Triggers on 'learn', 'save knowledge', or session ends.

3 tools

workflow

Stats

Stars21

Forks0

Last CommitApr 12, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Update CLAUDE.md

Overview

Which CLAUDE.md?

Find the CLAUDE.md you own in the current repo:

In ~/clawd/ — update your agent file (e.g. yuki/CLAUDE.md, kestrel/CLAUDE.md)

In any other repo — update the project root CLAUDE.md

If unsure, ask which file to update.

How to Update

Review the conversation — identify decisions, preferences, patterns, or conventions that were established

Read the current CLAUDE.md — understand what's already documented

Add only what's new — don't duplicate existing content

Place it in the right section — match the file's existing structure. Create a new section only if nothing fits.

Be concise — write it as an instruction, not a narrative. Future agents need to act on it, not read a story.

What to Capture

Workflow decisions ("always use X instead of Y")

Tool preferences ("use ttal pr, not gh")

Conventions discovered ("tests go in tests/ not test/")

Architecture decisions ("we chose X because Y")

Gotchas and warnings ("don't run Z, it breaks W")

What NOT to Capture

Session-specific details (current task, in-progress work)

Anything already in CLAUDE.md (check first!)

Speculative conclusions from one conversation

Temporary workarounds (unless they'll persist)

After Updating

Show the user what you added/changed

Commit if asked (follow the repo's commit conventions)