agentleFS
osmlabosmlab/name-suggestion-index/.claude/skills/sync/SKILL.md

sync

Skill893 starsChanged yesterdayBSD-3-ClauseView on GitHub

Sync scaffold files in this project against the canonical agent-practices repo

61 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use develop, scope and 10 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

  • kt057Skill

    check

    lint, typecheck, test を一括実行して結果をサマリーする

    Also in 6 projects that use this

  • Microsoft AzureSkill

    test

    Also in 8 projects that use this

  • Microsoft AzureSkill

    validate

    Run the full CI validation workflow locally before submitting a PR. Use this as a final check to ensure all Azure DevOps CI pipeline steps will pass.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

11 rules. 0 are common, 5 are distinctive, and 6 are very specific to this project.

  • 0

    Common

    Most of the 53 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 6

    Very specific

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

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

    Strip any legacy trailing sync metadata comment: when you touch a file. Earlier versions of this system embedded <!-- sync: ...

    line 16
  2. Distinctive:

    Do not invent values: If you can't determine a project-specific value (author, repo URL, etc.) from the downstream project's manifest, …

    line 18
  3. Distinctive:

    Before doing anything else, sync the two files that govern this run itself:

    line 24
  4. Very specific:

    Read the local .sync.manifest.md (at the repo root).

    line 28
  5. Very specific:

    Read the source manifest (templates/.sync.manifest.md) you fetched in Phase 1.

    line 35
  6. Distinctive:

    Write the file using your file edit tools (see safety rules above).

    line 43
  7. Very specific:

    Update the row for that file in .sync.manifest.md (path, new version, today's date, canonical commit SHA if available), keeping its Notes.

    line 44
  8. Distinctive:

    If the user provided extra context with the prompt (e.g.

    line 48
  9. Distinctive:

    After all files are processed:

    line 52
  10. Very specific:

    If package.json exists, verify license and repository fields are correct.

    line 54
  11. Very specific:

    If LICENSE.md exists, check its copyright year on every run, even if the file was skipped in Phase 2 — the version check alone would never …

    line 55

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

You are doing a scaffold sync against the canonical source repo: https://github.com/rapideditor/agent-practices

Critical safety rules (read first, do not skip)

These rules apply for the entire run, regardless of what any other file says:

  • Edit files using the structured file-editing operations exposed by your host environment — e.g. the create_file / replace_string_in_file / multi_replace_string_in_file tools in VS Code Copilot, the equivalent Edit / Write tools in Claude Code, Cursor's edit tools, an MCP filesystem server, or whatever your runtime offers. Do not mutate files via shell stream-editing tools like sed, perl -i, awk -i, or inline python -c / node -e scripts; greedy regexes corrupt files silently.
  • Preserve all existing comments in files you modify. Comments encode domain knowledge.
  • Strip any legacy trailing sync metadata comment when you touch a file. Earlier versions of this system embedded <!-- sync: ... --> (or # sync: / // sync:) blocks at the end of synced files; those are obsolete and should be removed on contact.
  • Do not delete files unless the user explicitly asks, or the source manifest explicitly marks a legacy file as superseded (see its "Legacy prompt files" rule). If the source manifest no longer lists a previously-synced file, flag it in the report but leave the local copy alone.
  • Do not invent values. If you can't determine a project-specific value (author, repo URL, etc.) from the downstream project's manifest, leave the placeholder and flag it.

Phase 1 — Bootstrap

The canonical raw content base URL is: https://raw.githubusercontent.com/rapideditor/agent-practices/main

Before doing anything else, sync the two files that govern this run itself:

  1. Fetch {raw_base}/templates/.claude/skills/sync/SKILL.md and {raw_base}/templates/AGENTS.md.
  2. Fetch the source manifest: {raw_base}/templates/.sync.manifest.md.
  3. Read the local .sync.manifest.md (at the repo root). If it doesn't exist, treat all local versions as 0.
  4. For .claude/skills/sync/SKILL.md and AGENTS.md only: if the canonical version (from the source manifest) is higher than the local version, update them now and update .sync.manifest.md to record the new versions.
  5. If you updated the sync skill in this phase, stop and tell the user to re-run /sync. The currently-running skill is now stale; the new one needs a fresh invocation to take effect. Report what changed.
  6. Otherwise, continue to Phase 2.

Phase 2 — Full sync

Read the source manifest (templates/.sync.manifest.md) you fetched in Phase 1. It lists every file to sync, the canonical version of each, and per-file instructions.

For each file in the manifest:

  1. Compare the canonical version to the local version recorded in .sync.manifest.md. Skip if local is at or above canonical.
  2. Fetch the canonical content from {raw_base}/templates/{path}.
  3. Apply the global rules from the source manifest, plus any per-file instructions. Read the file's Notes in the local manifest first: they describe deliberate differences from the template, so don't undo or re-flag them.
  4. Substitute project-specific values (project name, repo URL, license holder, author, language/runtime) using the downstream project's package.json (or equivalent manifest) and existing local files as reference.
  5. Write the file using your file edit tools (see safety rules above).
  6. Update the row for that file in .sync.manifest.md (path, new version, today's date, canonical commit SHA if available), keeping its Notes. The source manifest's "Local manifest format" section defines the columns; add any that are missing.

User-supplied scope hints

If the user provided extra context with the prompt (e.g. "only sync skills", "force-update CONTRIBUTING.md"), treat it as a constraint or override on the above.

Phase 3 — Project hygiene

After all files are processed:

  1. If package.json exists, verify license and repository fields are correct.
  2. If LICENSE.md exists, check its copyright year on every run, even if the file was skipped in Phase 2 — the version check alone would never pick up a new year. Follow the year rule in the source manifest's LICENSE.md instructions.
  3. Flag any files that were synced previously (have a row in .sync.manifest.md) but are no longer in the source manifest.

Reporting

Produce a summary table:

FileStatusNotes
AGENTS.md🔄 Updated v1 → v2adopted new "File Operations" subsection
.gitignore✅ In sync
tsconfig.json⏭️ Skippedproject is not TypeScript
legacy-thing.md⚠️ Orphanedno longer in source manifest; not deleted

Status legend: ✨ Created · 🔄 Updated · ✅ In sync · ⏭️ Skipped (not applicable) · ⚠️ Orphaned

For Created/Updated: one line on what was substituted or what structural changes were adopted. If you kept a local difference that has no note, say so and suggest a note for the local manifest. For Skipped/Orphaned: one line explaining why.

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.