agentleFS
VicentehersantVicentehersant/vhs-agents-and-skills/skills/site-sweep/SKILL.md

site-sweep

Skill0 starsChanged 38 days agoMITView on GitHub

Protocol for any "whole site" token/typography change (rename a token, swap a font, change a weight or color everywhere) — enumerate every affected page BEFORE editing, apply to all of them, verify with grep that no raw value survives. Use whenever the request implies "the whole site"/"everywhere", not a single page.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Verify with grep, not eyes: search the whole affected tree for the old raw value (old hex, px, font-family/weight string).

    line 17
  2. Distinctive:

    Every row from step 1 appears.

    line 20
  3. Distinctive:

    If the scope of "everywhere" is ambiguous (which routes count, shared component vs page-local override), ask before sweeping rather than …

    line 23

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “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

Site Sweep

Failure this fixes: an agent says "done" after fixing one or two pages, and the user finds the rest still broken page by page.

Procedure

  1. Enumerate BEFORE editing: glob/grep every file that can contain the old value (page routes, layouts/shared components, CSS/tokens, MDX/content). List them as a checklist — this is the scope, not a guess.
  2. Apply to every item, one by one. Don't skip a page because it "probably" already uses the token.
  3. Verify with grep, not eyes: search the whole affected tree for the old raw value (old hex, px, font-family/weight string). Zero hits = done.
  4. Report as a table: page/file → status (fixed / already correct / N/A). Every row from step 1 appears; none silently dropped.

When unclear, ask

If the scope of "everywhere" is ambiguous (which routes count, shared component vs page-local override), ask before sweeping rather than under-scoping.

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.