agentleFS
Sign inStart free
purpleeddypurpleeddy/cladding/skills/sync/SKILL.md

sync

Skill16 starsChanged 4 months agoMITView on GitHub

Validate the active spec.yaml against the Ironclad schema and refresh the inventory. Rarely needed manually — clad_create_feature already auto-syncs the inventory and clad check / clad done self-validate the spec, so do NOT run it as a reflexive pre-flight before those. Use it only after you have directly hand-edited a shard file (spec/features/*.yaml or spec.yaml). Activate only when the connected project contains spec.yaml or the user explicitly names Cladding; ignore ordinary requests in uninitialized projects.

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 45 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

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

    Run clad sync from the project root.

    line 7
  2. Very specific:

    clad_create_feature auto-syncs the inventory: after each feature it writes (and rejects a malformed AC at creation), so you don't need to …

    line 26
  3. Very specific:

    Run clad sync only when you have hand-edited a shard file directly (Edit/Write on spec/features/*.yaml or spec.yaml), to refresh the …

    line 31
  4. Very specific:

    Prefer clad_create_feature over hand-editing in the first place — then even this is unneeded.

    line 33

“Common” is measured: kept by at least 6 in 10 of the 45 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

Cladding sync

Run clad sync from the project root. The command:

  • Loads spec.yaml (or its sharded form under spec/features/*.yaml).
  • Validates against src/spec/schema.json (JSONSchema).
  • Reports the feature count and any validation failures.
  • Exits non-zero when the spec is invalid so CI can gate on it.

Spec must be valid before clad check or any stage runner produces meaningful output. If sync fails, fix the reported issues first.

clad sync

When you actually need it (don't reflex-sync)

You rarely need to run this MANUALLY — and a reflexive "just-in-case" sync after every operation is wasted work (in an A/B measurement, 28 of 30 manual clad sync calls found nothing to fix). The inventory + validation are already maintained for you:

  • clad_create_feature auto-syncs the inventory after each feature it writes (and rejects a malformed AC at creation), so you don't need to sync after creating features.
  • clad check / clad done validate the spec themselves (drift stage), so you don't need to pre-sync before them — a real drift surfaces in that gate anyway.

Run clad sync only when you have hand-edited a shard file directly (Edit/Write on spec/features/*.yaml or spec.yaml), to refresh the inventory and re-validate that edit. Prefer clad_create_feature over hand-editing in the first place — then even this is unneeded.

Download now (ZIP)

  • Other versions52 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 52

    1. microsoft/vscode★ 194ksame name
    2. jsmastery-pro/skills★ 1.4ksame name
    3. H-mmer/pentest-agents★ 815same name
    4. poingstudios/godot-admob-plugin★ 648same name
    5. cortex-tms/cortex-tms★ 180same name
    6. grainulation/grainulator★ 86same name
    7. lsnackerman/raw-clauding-skills★ 45same name
    8. fivetaku/tikeytaka★ 40same name
    9. namedtoaster/The-Last-Mile★ 37same name
    10. rlajous/claude-code-commands★ 30same name

    42 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects with it also use develop, scope and 7 more.

    Other files people use alongside this one.

    Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
    • hong9LeeSkill

      develop

      빌드, 아키텍처, git 관련 작업 시 OMS MSA 공통 인프라 규칙을 적용한다. 기술 스택, 빌드 명령, 헥사고날 아키텍처 구조, git 워크플로우, AI Context 동기화 규칙을 다룬다. 코드 작성 컨벤션은 /convention, 테스트 컨벤션은 /test-guide 스킬을 참조.

      Also in 6 projects that use this

    • YuriNachosSkill

      scope

      Configure claude-scope status line widgets for Claude Code. Use when user wants to customize widgets, change theme, reorder elements, or modify display style.

      Also in 7 projects that use this

    • nicolasestremSkill

      document

      Create focused documentation for specific components or features

      Also in 5 projects that use this

    • Microsoft AzureSkill

      test

      Also in 8 projects that use this

    • AnthropicSkill

      debug

      Structured debugging session — reproduce, isolate, diagnose, and fix. Trigger with an error message or stack trace, "this works in staging but not prod", "something broke after the deploy", or when behavior diverges from expected and the cause isn't obvious.

      Also in 10 projects that use this

    • Harut8Skill

      architect

      Also in 6 projects that use this

  • In this repository17 other files it gives its agents.

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