agentleFS
Sign inStart free
RevealUIStudioRevealUIStudio/revskills/skills/revealui-sync-rules/SKILL.md

revealui-sync-rules

Skill2 starsChanged 51 days agoMITView on GitHub

Verify agent rules distribution topology across RevealUI repos (revcon profiles, materialized copies). Prefer control-layer / revcon entrypoints; Claude hook path is one adapter. Read-only; never mutates without asking.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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:

    Run the topology check and report results.

    line 12
  2. Distinctive:

    Do not auto-fix. Report, then ask for direction.

    line 42

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Run the topology check and report results.

Entry points (first match wins)

# 1) Control-layer / revcon when available
if [ -x "$REVEALFLEET_ROOT/revcon/link.sh" ]; then
  # report-only: do not run link.sh without owner ask; prefer check scripts
  echo "revcon present: $REVEALFLEET_ROOT/revcon"
fi
if [ -f "$REVEALFLEET_ROOT/revskills/scripts/verify-copy-lockstep.sh" ]; then
  bash "$REVEALFLEET_ROOT/revskills/scripts/verify-copy-lockstep.sh" 2>/dev/null || true
fi

# 2) Claude adapter hook (legacy Studio path)
if [ -f "$HOME/.claude/hooks/sync-rules.sh" ]; then
  bash "$HOME/.claude/hooks/sync-rules.sh"
elif [ -f "$HOME/.claude/hooks/sync-rules.js" ]; then
  node "$HOME/.claude/hooks/sync-rules.js" 2>/dev/null || true
else
  echo "SKIP: no sync-rules entry on this machine — inspect revcon profiles + .claude/.revcon-manifest.json manually"
fi

How to interpret output (two sanctioned distribution modes):

  • <repo>: materialized — git-tracked copies + .claude/.revcon-manifest.json; content verification is that repo's rules-lockstep CI.
  • BROKEN SYMLINK / FOREIGN TARGET (exit 1) — fix on revcon side; report and ask before touching.
  • VENDORED COPY (warn) — regular file shadows profile rule without manifest; present options and ask.

Do not auto-fix. Report, then ask for direction.

Historical note: independent dual-copy diffs against the coordination hub were retired 2026-07-16.

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.

Check your setup, free