Skip to content
Development
Command

/sync-capabilities

Detect and fix drift between plugin.json registrations and capabilities reference documentation

From plugin
claude-night-market
343162 skills60 agents162 commands1 MCP
> /plugin marketplace add athola/claude-night-market

Command definition

sync-capabilities.md
description: Detect and fix drift between plugin.json registrations and capabilities reference documentation
usage: /sync-capabilities [--fix] [--plugin <name>]

Sync Capabilities

Compare plugin.json registrations (skills, commands, agents) against `book/src/reference/capabilities-reference.md` and report discrepancies. Optionally auto-generate missing entries.

Arguments

  • `--fix` - Auto-generate missing entries in capabilities-reference.md (default: report only)
  • `--plugin <name>` - Check a specific plugin instead of all plugins

Workflow

The detection script, the discrepancy types, and the entry templates are kept in one module: `plugins/sanctum/skills/doc-updates/modules/capabilities-sync.md`. Read that module, then:

1. Run its **Detection Script** from the repo root. 2. With `--plugin <name>`, keep only the report lines that name `<name>`. The script checks every plugin, and this filter is applied to its output. 3. With `--fix`, add each missing entry using the module's **Auto-Generation Templates**, in alphabetical order within its table in `book/src/reference/capabilities-reference.md`. 4. Re-run the check until it reports zero discrepancies. `make docs-sync-check` runs the CI version, `scripts/capabilities-sync-check.sh`, and exits 1 on any discrepancy.

Examples

# Report all discrepancies (dry run, default)
/sync-capabilities

# Check only the sanctum plugin
/sync-capabilities --plugin sanctum

# Auto-fix missing entries across all plugins
/sync-capabilities --fix

# Fix a specific plugin's missing entries
/sync-capabilities --fix --plugin abstract

When To Use

  • After adding new skills, commands, or agents to a plugin
  • During PR preparation to verify documentation is current
  • After `/update-plugins` to sync docs with registration changes
  • Periodically to catch documentation drift

When NOT To Use

  • During `/update-docs` (which already includes capabilities sync as Phase 4.75)
  • For plugin.json registration issues (use `/update-plugins` instead)

Integration

`/update-docs` runs the same check as Phase 4.75. Complements:

  • `/update-plugins`: syncs plugin.json with disk contents (the other

direction)

  • `/update-docs`: full documentation update including capabilities

sync

See Also

  • `plugins/sanctum/skills/doc-updates/modules/capabilities-sync.md` - Detection logic module
  • `book/src/reference/capabilities-reference.md` - Central capability listing
  • `/update-plugins` - Plugin registration audit
Read more
@athola
Ships withclaude-night-market

A plugin marketplace for Claude Code. Install only the plugins you need to run git workflows, code review, spec-driven development, and autonomous agents from inside your Claude Code session.

343200 skills60 agents1 MCP
Get the whole plugin

Stars on GitHub

Momentum

stars in total
343
Star history of athola/claude-night-market on GitHub, a chart by star-history.com

Other commands on claude-night-market.

More commands from other plugins.

build
Auto-invoked

build

Command

Implement tasks incrementally — build, test, verify, commit. Add "auto" to run the whole plan in one approved pass.

@addyosmani@addyosmaniInstall Command