sync-edit

Routes detected sync-check inconsistencies to the appropriate scoped role agent for correction.

1|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/hirokimry/vibecorp --skill sync-edit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync-edit
Source: https://github.com/hirokimry/vibecorp/tree/main/skills/sync-edit
Command: npx skills add https://github.com/hirokimry/vibecorp --skill sync-edit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill fixes inconsistencies found by sync-check without manual cross-editing, so each role agent can correct only the files it owns.

Core Features & Use Cases

  • Scoped remediation: Routes each detected mismatch to the correct agent, such as CTO, CPO, legal, accounting, or SM.
  • Safe file ownership: Enforces strict edit boundaries so agents only modify their own governed documents and knowledge paths.
  • Buffer-based knowledge updates: Uses the knowledge buffer worktree for role knowledge writes and avoids unsafe direct writes.
  • Use case: After a documentation or knowledge drift is detected, run this Skill to apply the right fixes, preserve ownership rules, and prepare the repository for a clean recheck.

Quick Start

Run /vibecorp:sync-edit after /vibecorp:sync-check to delegate each detected inconsistency to the appropriate role agent and apply the fixes.

Frequently Asked Questions about sync-edit

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

FAQPage Schema
How do I fix documentation inconsistencies detected across different role agents?

Fix documentation inconsistencies by routing detected mismatches to the correct role agents, such as CTO or CPO, ensuring each agent only modifies its own scoped files and knowledge paths.

What is scoped remediation for knowledge buffer worktrees?

Scoped remediation is a maintenance workflow that delegates knowledge buffer worktree fixes to specific role agents, enforcing strict file ownership so agents only update governed documents they control.

How do I enforce file ownership boundaries when applying documentation repairs?

Enforce file ownership boundaries by using sequential agent execution and strict file-scope enforcement, which prevents agents from directly modifying knowledge paths outside their designated worktree buffer.

Can I use this workflow for role-based maintenance across legal and accounting agents?

Yes, this workflow supports role-based maintenance for legal, accounting, and SM agents by delegating specific detected inconsistencies to each role for sequential execution and scoped remediation.

Do I need to run a validation check after applying documentation fixes?

Yes, you need to run a post-fix validation check using sync-check to verify that all role-based agent updates successfully resolved the detected knowledge and documentation drift.

What's the best way to prevent unsafe direct writes when updating role knowledge?

Prevent unsafe direct writes by routing all role knowledge updates through a dedicated knowledge buffer worktree, ensuring documentation repair respects strict edit boundaries and scoped file ownership.