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
- akovfoj-lang/plainframetheir own version, first seen Nov 16, 2026
- champ18ion/claud18codetheir own version, first seen Nov 16, 2026
- web3illy/private-second-brain-skillstheir own version, first seen Nov 16, 2026
- joryeugene/keephivetheir own version, first seen Nov 15, 2026
- muslim-sec/skillstheir own version, first seen Nov 15, 2026
- Trixx4191/asrartheir own version, first seen Nov 15, 2026
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.
hong9LeeSkilldevelop
빌드, 아키텍처, git 관련 작업 시 OMS MSA 공통 인프라 규칙을 적용한다. 기술 스택, 빌드 명령, 헥사고날 아키텍처 구조, git 워크플로우, AI Context 동기화 규칙을 다룬다. 코드 작성 컨벤션은 /convention, 테스트 컨벤션은 /test-guide 스킬을 참조.
Also in 6 projects that use this
YuriNachosSkillscope
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
nicolasestremSkilldocument
Create focused documentation for specific components or features
Also in 5 projects that use this
kt057Skillcheck
lint, typecheck, test を一括実行して結果をサマリーする
Also in 6 projects that use this
Microsoft AzureSkilltest
Also in 8 projects that use this
Microsoft AzureSkillvalidate
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
Other versions61 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 61
- microsoft/vscode★ 195ksame name
- jsmastery-pro/skills★ 1.4ksame name
- H-mmer/pentest-agents★ 815same name
- poingstudios/godot-admob-plugin★ 648same name
- cortex-tms/cortex-tms★ 180same name
- grainulation/grainulator★ 86same name
- lsnackerman/raw-clauding-skills★ 45same name
- fivetaku/tikeytaka★ 40same name
- namedtoaster/The-Last-Mile★ 39same name
- rlajous/claude-code-commands★ 30same name
51 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.
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
- Very specific: line 16
Strip any legacy trailing sync metadata comment: when you touch a file. Earlier versions of this system embedded <!-- sync: ...
- Distinctive: line 18
Do not invent values: If you can't determine a project-specific value (author, repo URL, etc.) from the downstream project's manifest, …
- Distinctive: line 24
Before doing anything else, sync the two files that govern this run itself:
- Very specific: line 28
Read the local .sync.manifest.md (at the repo root).
- Very specific: line 35
Read the source manifest (templates/.sync.manifest.md) you fetched in Phase 1.
- Distinctive: line 43
Write the file using your file edit tools (see safety rules above).
- Very specific: line 44
Update the row for that file in .sync.manifest.md (path, new version, today's date, canonical commit SHA if available), keeping its Notes.
- Distinctive: line 48
If the user provided extra context with the prompt (e.g.
- Distinctive: line 52
After all files are processed:
- Very specific: line 54
If package.json exists, verify license and repository fields are correct.
- Very specific: line 55
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 …
“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.
Files
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_filetools in VS Code Copilot, the equivalentEdit/Writetools 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 likesed,perl -i,awk -i, or inlinepython -c/node -escripts; 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:
- Fetch
{raw_base}/templates/.claude/skills/sync/SKILL.mdand{raw_base}/templates/AGENTS.md. - Fetch the source manifest:
{raw_base}/templates/.sync.manifest.md. - Read the local
.sync.manifest.md(at the repo root). If it doesn't exist, treat all local versions as0. - For
.claude/skills/sync/SKILL.mdandAGENTS.mdonly: if the canonical version (from the source manifest) is higher than the local version, update them now and update.sync.manifest.mdto record the new versions. - 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. - 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:
- Compare the canonical version to the local version recorded in
.sync.manifest.md. Skip if local is at or above canonical. - Fetch the canonical content from
{raw_base}/templates/{path}. - 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.
- 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. - Write the file using your file edit tools (see safety rules above).
- 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:
- If
package.jsonexists, verifylicenseandrepositoryfields are correct. - If
LICENSE.mdexists, 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'sLICENSE.mdinstructions. - 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:
| File | Status | Notes |
AGENTS.md | 🔄 Updated v1 → v2 | adopted new "File Operations" subsection |
.gitignore | ✅ In sync | |
tsconfig.json | ⏭️ Skipped | project is not TypeScript |
legacy-thing.md | ⚠️ Orphaned | no 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.
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
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.

