How do I install the Monorepo Sync skill?

Run npx skillmds@latest add thewatcher01/monorepo-sync in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Monorepo Sync safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Monorepo Sync?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Monorepo Sync free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Monorepo Sync?

TheWatcher01 (@thewatcher01) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Monorepo Sync by thewatcher01 — Agent Skill

Name: Monorepo Sync
Rating: 4.2 (5 reviews)
Author: TheWatcher01

File contents

Monorepo Sync — chainskills

Keeps all documentation and version metadata consistent across the cli-mcp-core/ and vscode-extension/ packages and the monorepo root.

Files to Keep in Sync

File	Purpose	Syncs With
`ROADMAP.md` (root)	Canonical roadmap — phases, changelog, decisions	—
`AGENTS.md` (root)	Monorepo index	`cli-mcp-core/AGENTS.md` + `vscode-extension/AGENTS.md`
`cli-mcp-core/package.json`	CLI version	`ROADMAP.md` changelog
`vscode-extension/package.json`	Extension version	`ROADMAP.md` changelog

Sync Protocol

On Version Milestone Completion

Mark phase complete in canonical roadmap (ROADMAP.md):
- Update phase status: En cours -> Complete (YYYY-MM-DD)
- Add changelog entry with features list and metrics
- Update "Phase suivante" section
Update AGENTS.md files:
- Root AGENTS.md: update phase status in roadmap table
- cli-mcp-core/AGENTS.md: same update
- Check that agent/skill references are still valid
Bump package versions (if applicable):
- cli-mcp-core/package.json -> version field
- vscode-extension/package.json -> version field

On New Agent/Skill/Instruction Added

Add entry to root AGENTS.md (agents table or skills table)
Add entry to relevant project AGENTS.md (cli-mcp-core/AGENTS.md or vscode-extension/AGENTS.md)
Verify applyTo patterns don't conflict with existing instructions

On README Update

Update cli-mcp-core/README.md for CLI/Core changes
Update vscode-extension/README.md for extension changes
Update root README.md if monorepo-level changes

Consistency Rules

No duplication: Root AGENTS.md = index only. Project AGENTS.md = project details.
Single source of truth: ROADMAP.md (root) — canonical roadmap for all packages.
Version parity: Both package versions should bump together for cross-cutting changes.
Link integrity: All markdown links in AGENTS.md files must resolve correctly.

Anti-patterns

Do not update canonical roadmap but not root roadmap
Do not add agent to project AGENTS.md but not root AGENTS.md
Do not allow different phase statuses between canonical and portfolio roadmaps
Do not bump version in package.json but not in ROADMAP.md changelog

---name: monorepo-syncdescription: Synchronize roadmaps, AGENTS.md, versions, and documentation across chainskills monorepo packages — use when updating version numbers, syncing roadmap status, or keeping documentation consistent---# Monorepo Sync — chainskillsKeeps all documentation and version metadata consistent across the `cli-mcp-core/` and `vscode-extension/` packages and the monorepo root.## Files to Keep in Sync| File | Purpose | Syncs With ||------|---------|------------|| `ROADMAP.md` (root) | Canonical roadmap — phases, changelog, decisions | — || `AGENTS.md` (root) | Monorepo index | `cli-mcp-core/AGENTS.md` + `vscode-extension/AGENTS.md` || `cli-mcp-core/package.json` | CLI version | `ROADMAP.md` changelog || `vscode-extension/package.json` | Extension version | `ROADMAP.md` changelog |## Sync Protocol### On Version Milestone Completion1. **Mark phase complete** in canonical roadmap (`ROADMAP.md`): - Update phase status: `En cours` -> `Complete (YYYY-MM-DD)` - Add changelog entry with features list and metrics - Update "Phase suivante" section2. **Update AGENTS.md files**: - Root `AGENTS.md`: update phase status in roadmap table - `cli-mcp-core/AGENTS.md`: same update - Check that agent/skill references are still valid3. **Bump package versions** (if applicable): - `cli-mcp-core/package.json` -> `version` field - `vscode-extension/package.json` -> `version` field### On New Agent/Skill/Instruction Added1. Add entry to root `AGENTS.md` (agents table or skills table)2. Add entry to relevant project AGENTS.md (`cli-mcp-core/AGENTS.md` or `vscode-extension/AGENTS.md`)3. Verify `applyTo` patterns don't conflict with existing instructions### On README Update1. Update `cli-mcp-core/README.md` for CLI/Core changes2. Update `vscode-extension/README.md` for extension changes3. Update root `README.md` if monorepo-level changes## Consistency Rules- **No duplication**: Root AGENTS.md = index only. Project AGENTS.md = project details.- **Single source of truth**: `ROADMAP.md` (root) — canonical roadmap for all packages.- **Version parity**: Both package versions should bump together for cross-cutting changes.- **Link integrity**: All markdown links in AGENTS.md files must resolve correctly.## Anti-patterns- Do not update canonical roadmap but not root roadmap- Do not add agent to project AGENTS.md but not root AGENTS.md- Do not allow different phase statuses between canonical and portfolio roadmaps- Do not bump version in package.json but not in ROADMAP.md changelog

Frequently asked questions

Monorepo Sync