sync
Run /sync as the last step after a change is complete, around merge, to keep durable knowledge current. Updates root and nested AGENTS.md, reconciles the scope from repo evidence, and flags specs the change made stale. Surgical edits only: it adds lines, and rewrites single lines it owns.
Install / Use
npx skills add jsmastery-pro/skills --skill syncInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Tags
Our assessment of sync
sync scores 85/100 on our quality scale, 2647th of 4,698 Development & Engineering skills we index.
Its SKILL.md is 15 KB long, well organised into 14 sections with 1 code example: a thorough specification that gives an agent plenty to work with.
With 1,318 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 3 months ago. That is recent enough to be usable, but agent tooling moves fast, so check the instructions against your agent's current version.
- Our last check on 2026-10-30 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit β read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-04. Automated pattern scan on 2026-10-04. It catches known dangerous patterns, not every risk β read a skill before letting an agent act on it.
sync compared with similar skills
All 4 of these similar skills score higher than sync; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| sync (this skill)by jsmastery-pro | 85 | 1.3k | 3mo ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 72.1k | today | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 47.3k | 2d ago | CLAUDE.md |
| lobehubby lobehub | 100 | 85.6k | today | MCP Server |
Frequently asked questions
- How do I install sync?
- Run
npx skills add jsmastery-pro/skills --skill sync. The install tabs above show the steps for each supported agent. - Which AI agents does sync work with?
- It is written for OpenAI Codex, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is sync safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is sync still maintained?
- The repository was last updated about 3 months ago. That is recent enough to be usable, but agent tooling moves fast, so check the instructions against your agent's current version.
Skill content
View source on GitHubname: sync allowed-tools: Bash, Read, Grep, Glob, Write, Edit, Agent description: "Run /sync as the last step after a change is complete, around merge, to keep durable knowledge current. Updates root and nested AGENTS.md, reconciles the scope from repo evidence, and flags specs the change made stale. Surgical edits only: it adds lines, and rewrites single lines it owns. Never a whole section, never curated prose."
Output style (plain words, no dashes, no hyphens)
<!-- OUTPUT-STYLE:START -->Write everything this skill produces, files and messages alike, in plain simple language. Talk to the reader as you, warm and direct like a colleague, and present every step as a recommendation they may run or skip, never an order. Keep technical terms that carry real meaning; explain each in plain words. Never use a dash or a hyphen as punctuation: no em dash, no en dash, and no hyphenated compounds. Write read only, not read-only. Say it in simple words, or reword the sentence. Code, file paths, command flags, and values other skills match on keep their hyphens. Use short sentences, commas, or parentheses. Clear beats clever.
What this skill does
Closes the loop on a completed change: syncs AGENTS.md files, the scope, and linked spec **Status**: lines to what the repo now shows, and flags what it must not edit (stale specs, curated prose). The Boundaries table below is the exact contract.
agent-prompt.md is the single source of truth for the maintenance rules; SKILL.md covers only orchestration. The main thread reads it and does the maintenance itself (see Step 3).
Canonical file: durable context lives in the tool agnostic AGENTS.md; CLAUDE.md is only a pointer to it. /sync edits/creates both, treating them only as targets, never as a change source.
Boundaries
| Action | /sync | Owner |
|---|---|---|
| Edit existing root/nested AGENTS.md | β
maintains | /sync |
| Reconcile root AGENTS.md's ## Build approach line to the scope header's approach (surgical single line edit, like the stack) | β
maintains; flags a curated divergence | /sync |
| Add a one line pointer to design.md (the UI design system) in the nearest AGENTS.md when a change establishes one | β
maintains (pointer only) | /sync |
| Create nested <area>/AGENTS.md for an area net new in this change | β
creates (diff = full area context) + adds root pointer | /sync |
| Create nested doc for an already existing undocumented area (only sliced by the diff) | β flags "run /audit" | /audit |
| Create or restructure the root AGENTS.md | β flags "run /audit" | /audit |
| Reconcile a spec's **Status**: line to its feature's scope status (plannedβProposed, in-progressβIn Progress, doneβAccepted; an Assumed spec is the exception: leave it Assumed and surface it, never reconcile it to Accepted) | β
Status line only | /sync |
| Clear an Assumed spec (move it out of Assumed) | β flags as decision debt "run /architect to ratify" (never reconciled to the feature status; only ratification clears it) | /architect |
| Edit a spec's content / supersede it | β flags as stale | /architect |
| Reconcile the scope, for the relevant workspace's scope file only (not all of docs/scope/), tick any completed sub task from repo evidence (code, tests, AGENTS.md), advance status | β
corrects | /sync |
| Add / reorder features or sub tasks in the scope | β leaves alone | /scope |
| Overwrite or rewrite curated AGENTS.md prose | β flags conflict instead | human |
The dividing line on creation is context, not policy: create only when this change shows you the whole area; defer to /audit when the area predates the change and you've seen only a slice. When unsure, flag instead of creating.
Asks vs acts
Acts. Pauses only when there is nothing to sync (empty change set). Every edit to curated files is listed in the report so you can review or revert.
Artifact ownership
Owns exactly what the Boundaries table grants and writes nothing else. As the universal sub task reconciler it ticks any scope sub task it can verify from repo evidence (sweeping the /test//audit//sync sub tasks other skills don't tick) and advances feature status; exact rules in agent-prompt.md.
Artifact base. specs and the scope live under docs/ by default, or .workflow/ if docs/ is a published docs site; use whichever base exists in the repo (paths here assume docs/).
Portability (any OS, any agent)
- Commands:
gitis the only required CLI and behaves the same on every OS, run thegitlines as shown. Other shell snippets are POSIX reference, not literal scripts: don't assumefind,grep,sed,cat,test/[ ],ls, orxargsexist; use your agent's cross platform file tools and apply branching logic yourself rather than shellif/variables/redirects. - Bundled files: referenced by paths relative to this skill's folder. Resolve the folder to an absolute path (you already resolve these relative paths) and read
agent-prompt.mdyourself at write time (Step 3), not during the earlier steps. - The whole maintenance runs inline on the main thread, following the exact rules in
agent-prompt.md(authoritative).
Execution
1. Scope the change set (cheap, with per file status)
Freshness first (teams): git fetch --quiet; if git rev-list --count HEAD..origin/$BASE > 0 you are behind origin/$BASE, warn the engineer to pull first, a teammate may have already synced these docs.
Base: main if git rev-parse --verify main succeeds, else master. Current branch: git rev-parse --abbrev-ref HEAD. Use --name-status (not --name-only); the net new area and orphan cleanup logic need Added vs Modified vs Deleted per file.
- Current branch is the base, mode
uncommitted:git diff --name-status HEAD. - Otherwise, mode
branch:git merge-base "$BASE" HEAD, thengit diff --name-status <merge-base>.
Either way, add untracked files from git ls-files --others --exclude-standard, each prefixed with an A status (matching the --name-status format). Note the mode, base, and merge base for the write step.
Remove duplicates, then filter to source files to sync from:
- Drop documentation and config (
AGENTS.mdat any level,docs/**,*.md,test-preferences.json, lock files, generated output); /sync reads these as targets/context, never as a change source. - Drop test files (
*.test.*,*.spec.*,__tests__/, etc.); tests aren't durable area conventions. - Keep the
D(deleted) entries in a separate list; they drive orphan cleanup (Step 3) though they aren't synced from. - Keep dependency manifest changes in a separate list for tool discovery, even if they are config rather than source:
package.json,pyproject.toml,requirements*.txt,go.mod,Cargo.toml,composer.json,Gemfile,pubspec.yaml,mix.exs,*.csproj, and equivalent package manifests. Lock files are signals only; do not pass lockfile contents.
If no source files and no dependency manifest changes remain (only docs/tests/lock/generated files changed), stop, nothing to sync. Do not spawn.
2. Locate the context files and specs (paths only, do NOT read them here)
Using your agent's file search/glob tools:
- Note whether a root
AGENTS.mdexists. - Find every
AGENTS.md(root + nested), excludingnode_modules/and.git/. - Find all specs under
docs/specs/whose names start with a digit, sorted. - Find the scope file(s) whose workspace/features the diff actually touches (in a monorepo, a changed file's workspace
apps/<x>/β¦selectsdocs/scope/<x>/); never read or pass all ofdocs/scope/.
Note the paths plus the changed file list and diff command; read the files at write time. Read root AGENTS.md contents now (short and useful to anchor on). For each changed file, note its nearest enclosing directory with a AGENTS.md (root or nested); that's the context file most likely to need an update.
2.5 Discover Agent Skills and optional MCPs for newly added tools
Run only when dependency manifests changed or the diff clearly adds a significant external tool. Skip ordinary utility libraries unless they define a durable workflow or integration.
-
Identify newly added significant packages/tools from the manifest diff, not the full lockfile: framework, router, styling/UI kit, database, ORM/query layer, auth/session, payments, email/notifications, storage/uploads, search, queue/background jobs, AI provider/vector DB, browser/runtime testing, observability, hosting/deploy. Include package names and common aliases from manifests. Do not stop after the first technology.
-
Filter out anything already covered by installed skills, connected MCPs, or
AGENTS.mddeclined entries. -
Ask before you search.
<!-- TOOL-CONSENT:START (identical in /architect, /audit and /sync; edit all or none) -->Asking is mandatory. Searching is not. Nothing is searched, fetched, installed, or spawned for Agent Skill and MCP discovery until the engineer has picked. Offer four choices: find them for me, I will name the ones I want, no and record the decline, or not now. Only the first may run a search command. Never silently skip the offer, and never run a search before the engineer agrees to one.
<!-- TOOL-CONSENT:END -->Name the tools this change added, say in one line that an Agent Skill gives the agent that tool's real conventions and an MCP server gives it live access to the real system, then ask: "Want me to find Agent Skills and MCP servers for the tools this change added?" (header
Agent skills), withYes, find them for me(recommended) Β·I'll name the ones I wantΒ·No, skip itΒ·Not now, later. OnYescontinue below. OnI'll name the ones I want, take the list and go straight to the install step, searching for nothing. OnNo, skip itrun nothing and record the decline. OnNot now, laterrun nothing and note the candidate tools in the report. -
Isolate the searches in a read only subagent (capability first, only after
Yes). Hand the remaining set to a discovery subagent rather than searching on the main thread: spawn it in the background (it does not block) if your agent supports that, else blocking; set its model explicitly to a fast, low cost tier (do not inherit the session model; on Claude Code spawn it as theresearchersubagent type, which pins the model); it returns only the compact candidate list. This keeps the search output out of/sync's bounded context. No subagent β search inline; no search capability β skip and note it. The offer panel stays on the main thread. -
For each remaining item, run
npx skills find <tool-or-package>; if weak, retry aliases from package/org names. Collect every credible Agent Skill candidate and confirm withnpx skills add <owner>/<repo> --listwhen practical. If the CLI is interactive/unavailable, search"<tool>" "agent skill"and confirm before offering. -
MCP search is optional: connector list first, else
"<tool>" "MCP server"per item. MCP is recommended upside, not required. -
Keep discovery capped and cacheable: max 5 web searches and 8 fetched pages total, official registry/docs first. Reuse
docs/.agent-cache/tool-discovery/<slug>.mdwhen under 30 days old, after filtering installed/declined items. -
Offer all Agent Skill matches in one multi select panel, grouped by technology: "Install relevant Agent Skills for newly added tools?" plus skip/decline. Then offer MCPs separately: "Optional MCP servers that could help these tools" plus skip/decline. Never install or connect automatically.
-
Install selected skills with
npx skills add <owner>/<repo> -y. For MCPs, point to the user's connector/MCP settings; once connected the tools are used automatically. -
Carry the result as
INSTALLED_SKILLS_OR_NONE,MCP_SERVERS_OR_NONE, and `DEC
Truncated for display β read the full file on GitHub.
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
ai-job-search
72.1kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
47.3kA visual, example-driven guide to Claude Code β from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
lobehub
85.6kπ€― LobeHub - Super-Agents on Your Team. Add super-agents to the chats your team already uses.They take on work by themselves and get better every week.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit β see the Safety scan above for what the skill file itself contains.
