Skip to content
Back to skills

Claude Md

ASecurity

Keep the CLAUDE.md your agents rely on accurate and lean instead of stale. Use when maintaining (not first creating) a CLAUDE.md — syncing it with architecture, conventions and commands as the project evolves, and pruning bloat so it stays scannable. Complements the built-in /init by owning the ongoing upkeep.

  • 4 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added June 4, 2026
ai-agentsgo

Security analysis

A100/100

Scanned June 4, 2026

npx -y skills add sp-daewoon/chronicle --skill claude-md --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Claude Md?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Claude Md
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/sp-daewoon-claude-md/badge)](https://www.skillsdirectory.com/skills/sp-daewoon-claude-md)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: claude-md
description: Keep the CLAUDE.md your agents rely on accurate and lean instead of stale. Use when maintaining (not first creating) a CLAUDE.md — syncing it with architecture, conventions and commands as the project evolves, and pruning bloat so it stays scannable. Complements the built-in /init by owning the ongoing upkeep.
license: MIT
---

# CLAUDE.md Maintenance Workflow

Keep an existing `CLAUDE.md` accurate and lean. This is for ongoing upkeep — use the built-in `/init` for first creation.

## Process

1. Read the current `CLAUDE.md`.
2. Compare against reality: recent commits, changed build commands, new/removed modules, updated conventions, new architecture decisions (check the ADR directory).
3. Update **only the affected sections**. Do not rewrite untouched sections.
4. Prune: remove stale instructions, merge duplicates, and keep each section tight. If a section has grown long, tighten it rather than letting it sprawl.
5. Preserve the user's voice and structure — you are maintaining their file, not replacing it.

## What to check for drift

- Build / test / lint commands that changed
- Module or directory structure changes
- New conventions or rules the team adopted
- Architecture decisions recorded as ADRs that belong in the high-level guidance
- Anything now contradicted by the actual codebase

## Rules

- Never blow away existing content wholesale — edit surgically.
- Keep it scannable; CLAUDE.md is loaded into every session, so brevity matters.
- If something is already obvious from the code or another doc, don't duplicate it here.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.