sync-specs
Use when code changes may have made documentation outdated, when reviewing docs for consistency, or when the user asks to sync or audit documentation.
Profile →npx skills add nexu-io/nexu --skill sync-specs --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Documentation Sync Review code changes and update project documentation for consistency. ## Mode | Mode | How to activate | Behavior | |------|----------------|----------| | `delta` (default) | No argument, or say "delta" | Diff against merge-base with `origin/main` + working tree changes | | `full` | Say "full audit" or "full sync" | Complete audit of all docs against current codebase | | Scope keyword | Say the keyword (e.g. "db", "api") | Targeted check (see Scope Filters below) | ## Delta Mode Baseline Identify changed files using merge-base (not a fixed commit count): ```bash # Branch changes since diverging from main git diff --name-only $(git merge-base HEAD origin/main)...HEAD # Plus staged + unstaged git diff --name-only --cached git diff --name-only ``` Combine the results into a single list of changed files. Then use the Impact Mapping to identify which docs may need updates. ## Impact Mapping Map changed areas to the docs they affect: | Changed area | Affected docs | |---|---| | `apps/controller/src/routes/` | `specs/references/api-patterns.md`, `ARCHITECTURE.md`, `specs/product-specs/*.md` (if route is user-facing) | | `apps/web/src/pages/` or `apps/web/src/app.tsx`
- Mode
- Delta Mode Baseline
- Impact Mapping
- Cross-Reference Pairs
- Scope Filters
- Rules
- Workflow
Branch changes since diverging from main git diff --name-only $(git merge-base HEAD origin/main)...HEAD Plus staged + unstaged git diff --name-only --cached git diff --name-only
What does the sync-specs skill do?
Use when code changes may have made documentation outdated, when reviewing docs for consistency, or when the user asks to sync or audit documentation.
How do I install it?
Run `npx skills add nexu-io/nexu --skill sync-specs --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From nexu-io/nexu, a repository with 3,239 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.