sync-workspace-structure

Scan workspace directories and update _index.md and CLAUDE.md files via templates.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/wuji-technology/pm-workflow-plugin --skill sync-workspace-structure
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync-workspace-structure
Source: https://github.com/wuji-technology/pm-workflow-plugin/tree/main/skills/sync-workspace-structure
Command: npx skills add https://github.com/wuji-technology/pm-workflow-plugin --skill sync-workspace-structure

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Synchronizes distributed index files and repository mappings so that changes to workspace directories, products, and skill definitions do not leave stale or inconsistent _index.md and CLAUDE.md metadata across personal and team repositories.

Core Features & Use Cases

  • Index maintenance: Scan directories, detect added/removed/renamed files and subdirectories, and update corresponding _index.md files using templates.
  • Repository sync workflow: Create precise local commits, prepare squash branches, and open PRs to protected team and plugin remotes before pushing origin.
  • Selective updates & safety: Only stage and commit index-related files, enforce PR-based merges for protected branches, and validate PR merge status prior to origin push.
  • Use case: After adding a new product directory or modifying .claude/skills, run the Skill to regenerate indexes, create team and plugin PRs, and await approvals before pushing to origin.

Quick Start

Run the sync-workspace-structure skill to scan changed paths, update affected _index.md and CLAUDE.md entries, create squash PRs for team and plugin remotes, and prepare to push to origin after merges.

Frequently Asked Questions about sync-workspace-structure

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I keep workspace indexes and repository mappings synced after directory changes?

Synchronizing workspace indexes involves scanning changed directories via glob patterns and applying template-driven updates to _index.md and CLAUDE.md files, ensuring distributed documentation and product portfolio metadata remain consistent.

What is the best way to update _index.md files when adding new product directories?

Updating _index.md files is handled by running a scan that detects new product directories and automatically regenerates affected index entries using predefined templates, ensuring distributed documentation stays consistent.

How does squash PR creation work for protected team and plugin remotes?

Squash PR creation for protected remotes works by staging only index-related files into a precise local commit, preparing a squash branch, and opening a pull request against the protected remote, validating merge status before pushing to origin.

Can I selectively stage only index files when preparing team and plugin PRs?

Selective staging is supported when preparing PRs, as the Skill only stages and commits index-related files like _index.md and CLAUDE.md, preventing unrelated directory modifications from entering the squash branch.

Do I need to validate PR merge status before pushing to origin?

Yes, validating PR merge status before pushing to origin is required, as the Skill enforces PR-based merges for protected team and plugin remotes and awaits approvals to ensure stale metadata is not pushed.

When should I not use automated workspace structure synchronization?

Automated workspace structure synchronization should not be used when modifying files outside of .claude/skills or assets standards, as the template-driven _index.md updates target directory creation, deletion, renaming, and portfolio additions specifically.