agentsclimarketplace

Proofread claude md

Skill davcs86/xstockstrat/.claude/skills/proofread-claude-md

Advisory read-only content review of CLAUDE.md files — flags stale file/service references, contradictions with the root CLAUDE.md (service registry, ports, language and tool versions, config governance, branch strategy), and missing critical info. Reports findings; never edits. Usage — /proofread-claude-md [file...]. Use this whenever the user asks to audit, proofread, sanity-check, or verify that CLAUDE.md / agent instructions / project memory are still accurate — and proactively after renaming a service, changing a port, bumping a language or tool version, or moving docs, since those are exactly what silently goes stale. To author a new CLAUDE.md from scratch, use /init instead.From its SKILL.md

Install
npx -y skills add davcs86/xstockstrat --skill proofread-claude-md

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

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 1 stars1 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.

SKILL.md

2.7 KB, as published. Nobody here has run it

Review the specified CLAUDE.md file(s) for content correctness. Runs entirely with the Read tool inside the current session — no external API calls.

Arguments

  • $ARGUMENTS — space-separated file paths (optional). If absent, find and review all CLAUDE.md files in the repo.

Steps

1. Collect files

If $ARGUMENTS is non-empty: use the provided paths as the file list.

Otherwise:

find . -name "CLAUDE.md" -not -path "*/.git/*" | sort

2. Load source of truth

Before reviewing any file, read the root CLAUDE.md in full — it is the authoritative source for:

  • Service names and their gRPC/HTTP ports (§Service Registry)
  • Language versions and tooling (§Language Versions & Tooling)
  • Config governance rules (§Config Governance Rules)
  • Branch strategy and merge rules (§Branch Strategy)

3. Review each file

For each file in the list, use the Read tool to read it in full, then check for:

  1. Stale references — port numbers, service names, tool versions, or file paths that conflict with root CLAUDE.md or are self-inconsistent
  2. Internal contradictions — two instructions within the same file that cannot both be correct
  3. Root CLAUDE.md contradictions — instructions that conflict with root-level governance (config keys, branch rules, migration conventions, etc.)
  4. Missing critical info — a section tells developers to do X but omits the concrete command or path they need to act on it

4. Print results per file

For each file:

=== path/to/CLAUDE.md ===
1. <one-sentence issue description>
2. <one-sentence issue description>
   (or "No issues found.")

5. Print summary

Reviewed N file(s). Issues found in M file(s).

Rules

  • Flag concrete, actionable issues only — not style or rewrites
  • One sentence per issue
  • Do not skip files with no issues — print "No issues found." for them
  • Do not modify any files

Keep looking

Skills are one crate of 608,475. 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.