agentleFS
paulo-yamagishipaulo-yamagishi/claude-code-setup/.claude/skills/update-readme/SKILL.md

update-readme

Skill2 starsChanged 9 months agoMITView on GitHub

Sync README.md with current skill capabilities and repo state

8 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read skill/SKILL.md — extract all audit categories, checks per category, and feature descriptions

    line 18
  2. Very specific:

    Read .claude/skills/bootstrap/SKILL.md — extract all phases, capabilities, and supported stacks

    line 19
  3. Distinctive:

    Keep descriptions concise — match the existing tone

    line 36

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Update README

Sync the README.md with the current state of /setup and /bootstrap skills.

Steps

  1. Read current skill definitions:
    • Read skill/SKILL.md — extract all audit categories, checks per category, and feature descriptions
    • Read .claude/skills/bootstrap/SKILL.md — extract all phases, capabilities, and supported stacks
  2. Read README.md and identify sections that reference skill features:
    • "What Gets Audited" table or list
    • Usage examples and command syntax
    • Feature descriptions and capability claims
    • Phase/step counts for bootstrap
  3. Diff skill state vs README:
    • Flag any audit category in the skill but missing from README
    • Flag any check count that doesn't match
    • Flag any bootstrap phase or capability not reflected in README
    • Flag any removed feature still mentioned in README
  4. Update README sections:
    • Edit only the stale sections — do not rewrite unrelated content
    • Preserve existing markdown style: tables, code blocks, heading levels
    • Keep descriptions concise — match the existing tone
  5. Report changes — list each section updated with a one-line summary of what changed.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.