MultiClaude: Command for Claude Code

.claude/commands/docs/sync.md

sync is a command for Claude Code from nguyennguyenit/MultiClaude. It costs 17 tokens per session (624 once invoked), scanned A, original, MIT.

A command that compares project documentation with the implementation and updates differences. It checks API routes, database schemas, and optionally user-interface components.

In plain words
What is it for?
Use it after implementation work to update API_SPEC.md, DB_DESIGN.md, or, when requested, UI_SPEC.md with actual endpoints, data structures, indexes, relationships, and components.
Why use it?
Documentation can become inaccurate after backend or frontend changes; this command brings it back in line with the code.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

This is nguyennguyenit/MultiClaude's own configuration. It tells Claude Code how to work on MultiClaude itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything MultiClaude configures →

Reuse

Borrowing it

Nothing to install: this file belongs to nguyennguyenit/MultiClaude. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/nguyennguyenit/MultiClaude/master/.claude/commands/docs/sync.md
Clone the repo
git clone --depth 1 https://github.com/nguyennguyenit/MultiClaude

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for sync

README.md
[![agentmods](https://agentmods.dev/badge/commands/nguyennguyenit/multiclaude/sync/github.svg)](https://agentmods.dev/commands/nguyennguyenit/multiclaude/sync)
Your own site
<a href="https://agentmods.dev/commands/nguyennguyenit/multiclaude/sync"><img src="https://agentmods.dev/badge/commands/nguyennguyenit/multiclaude/sync/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for sync

Your own site · 80×15
<a href="https://agentmods.dev/commands/nguyennguyenit/multiclaude/sync"><img src="https://agentmods.dev/badge/commands/nguyennguyenit/multiclaude/sync.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 624 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00017 $0.00624
Opus 5.5 $0.00007 $0.00250
Sonnet 5.5 $0.00003 $0.00125
Haiku 4.5 $0.00002 $0.00062

Measured 2mo ago against content hash 575cb3e84d07, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

sync scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/commands/docs/sync.md · 111 lines

How it starts

The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Purpose

Sync IPA-generated documentation with actual implementation after /code completion.


Docs to Sync

Doc Sync From When
docs/API_SPEC.md Actual API endpoints in codebase After BE tasks
docs/DB_DESIGN.md Actual database schema After BE tasks
docs/UI_SPEC.md Actual UI components After FE tasks (if changed)

Workflow

Step 1: Detect Changes

  1. Read current docs/API_SPEC.md
  2. Scan codebase for actual API endpoints:
    • Look for route definitions (Express, NestJS, FastAPI, etc.)
    • Extract request/response types
  3. Compare and identify differences

Step 2: Update API_SPEC.md

If differences found:

  1. Update endpoint list
  2. Update request/response schemas
  3. Update error codes
  4. Update Endpoint Matrix Status column:
    • ⏳ → ✅ (when endpoint is implemented)
    • ✅ → 🔄 (when docs match code exactly)
  5. Preserve manual notes/comments

Step 3: Update DB_DESIGN.md

  1. Read actual database schema (Drizzle, Prisma, TypeORM, etc.)
  2. Compare with docs/DB_DESIGN.md
  3. Update:
    • Table definitions
    • Column types
    • Relationships
    • Indexes

Step 4: Update UI_SPEC.md (if requested)

Only if $ARGUMENTS contains "ui" or "all":

  1. Scan UI components
  2. Update screen list
  3. Update component specs

Usage

# Sync API and DB docs (default after BE)
/docs:sync

# Sync all including UI
/docs:sync all

# Sync specific doc
/docs:sync api
/docs:sync db
/docs:sync ui

Output

Report changes made:

## Docs Sync Report

### API_SPEC.md
- Added: POST /api/users/register
- Updated: GET /api/users/:id response schema
- Removed: (none)
- **Status Updates:**
  - POST /auth/login: ⏳ → ✅
  - POST /auth/register: ⏳ → ✅
  - GET /users/:id: ⏳ → 🔄 (synced)

### DB_DESIGN.md
- Added: sessions table
- Updated: users table (added email_verified column)
- Removed: (none)

### UI_SPEC.md
- (not synced - use /docs:sync ui)

Important

  • Preserve manual notes: Don't overwrite human-added comments
  • Backup before sync: Create backup if significant changes
  • Review changes: Show diff before applying

Read the full file on GitHub · 111 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2mo ago First seen · 111 lines · 17 tokens per session scan A 575cb3e84d07

Subscribe to this mod's changes

sync is a command published in the GitHub repository nguyennguyenit/MultiClaude (23 stars, last pushed 2mo ago), licensed MIT. It adds 17 tokens to every session and 624 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

sync compared with commands from other repositories

sync next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
syncnguyennguyenit/MultiClaudeCommand232mo agoMITA17Claude Code
checklistgithub/spec-kitCommand148kyesterdayMITA13Claude Code
clarifygithub/spec-kitCommand148kyesterdayMITA27Claude Code
specifygithub/spec-kitCommand148kyesterdayMITA13Claude Code
analyzegithub/spec-kitCommand148kyesterdayMITA26Claude Code
convergegithub/spec-kitCommand148kyesterdayMITA35Claude Code
implementgithub/spec-kitCommand148kyesterdayMITA14Claude Code