agentsclimarketplace

Claude md

Skill sp-daewoon/chronicle/skills/claude-md

📜 Never write changelogs or release notes by hand again — automate your entire docs lifecycle (ADR · changelog · release · devlog · index) with 6 zero-dependency Claude Code skills.

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

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

1.6 KB, as published. Nobody here has run it

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.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.