sync
Skill5 starsChanged 44 days agoMITView on GitHub
User-invoked only. Post-pull sync — checks for missing .env vars, installs dependencies, and builds.
- Reads credentials
- Installs packages
57 other projects use a version of this.
Adopted by
Most recently taken up by
- 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
- grainulation/grainulatortheir own version, first seen Nov 12, 2026
- Catherine1401/agent-skillstheir own version, first seen Nov 8, 2026
- FabianoArthur/claude-code-kitchentheir own version, first seen Nov 8, 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 versions57 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 57
- 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
47 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.
In this repository24 other files it gives its agents.
- AGENTS.mdAGENTS.md
- assign-epicSkill
- briefingSkill
- bump-versionSkill
- captureSkill
- consultantSkill
- dependabot-reviewSkill
- fix-cicdSkill
- log-timeSkill
- morlockSkill
- morningSkill
- multi-repoSkill
- nightly-checkSkill
- pickupSkill
- pr-action-review-mine-loopSkill
- pr-action-reviewSkill
- pr-choreSkill
- pr-review-loopSkill
- prSkill
- pushSkill
- qa-review-actionSkill
- refineSkill
- runSkill
- wrap-upSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 1 is distinctive, and 3 are very specific to this project.
0
Common
Most of the 49 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
If .env does not exist, warn the user and stop:
- Very specific: line 18
If any keys from .env.example are absent from .env, list them:
- Very specific: line 24
If all keys are present, report: ".env is up to date."
- Distinctive: line 26
If there are missing variables or missing files, stop here and ask the user to resolve them before continuing.
“Common” is measured: kept by at least 6 in 10 of the 49 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
Your Task
Step 1 — Check for missing .env variables
Compare the keys in .env.example against your .env.
If .env does not exist, warn the user and stop:
.envdoes not exist. Copy from.env.exampleand fill in the values before continuing.
If any keys from .env.example are absent from .env, list them:
.envis missing the following variables (added to.env.example):
VARIABLE_NAME
If all keys are present, report: ".env is up to date."
If there are missing variables or missing files, stop here and ask the user to resolve them before continuing.
Step 2 — Install dependencies
Run: npm install
Report success or any errors. If npm install fails, stop and surface the error — do not continue.
Step 3 — Build
Run: npm run build
Report success or any errors.
Summary
End with a clear status block:
✓ .env — up to date
✓ npm install — complete
✓ build — complete
You're in sync with main.Or if something failed or was skipped, reflect that clearly.
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.

