auto-project-sync

Update CLAUDE.md, MEMORY.md, and project indexes after work batches.

6|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/Kgan01/ghengis-skills --skill auto-project-sync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auto-project-sync
Source: https://github.com/Kgan01/ghengis-skills/tree/main/plugins/ghengis-skills/skills/auto-project-sync
Command: npx skills add https://github.com/Kgan01/ghengis-skills --skill auto-project-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Update project documentation after a significant work batch to keep CLAUDE.md, MEMORY.md, and related indexes aligned with reality.

Core Features & Use Cases

  • Auto-updates CLAUDE.md with active phase decisions, MEMORY.md with session learnings, and CONTEXT/indexes to reflect new plans and permissions.
  • Global permission ratchet: promote reusable permissions from project-local to user-wide settings to reduce prompts and enforce consistency.
  • Use Case: After finishing a deployment, run the sync to consolidate decisions, capture lessons, and broadcast changes across projects.

Quick Start

Run /sync after completing a major work batch to automatically update CLAUDE.md, MEMORY.md, project indexes, and permission settings.

Frequently Asked Questions about auto-project-sync

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

FAQPage Schema
How do I automatically update CLAUDE.md and MEMORY.md after finishing a feature build?

To automate project documentation updates, run a post-batch sync to automatically update CLAUDE.md, MEMORY.md, and project indexes with new decisions, session learnings, and global permissions.

What is a global permission ratchet and how does it work for multi-agent runs?

A global permission ratchet promotes reusable permissions from project-local settings to user-wide settings, reducing prompts and enforcing consistency across multi-agent runs and major work batches.

How do I keep project indexes aligned with reality after a deployment?

You can keep project indexes aligned by running an automated post-batch sync that applies validation and idempotency to consolidate decisions, capture lessons, and broadcast changes across projects.

Does post-batch project sync include safe error handling for workflow coordination?

Yes, post-batch project sync includes safe error handling and validation to ensure end-to-end workflow coordination maintains a traceable history and consistent global settings during updates.

When should I run a project documentation sync for my automation workflow?

You should run a project documentation sync after completing major work batches, feature builds, or multi-agent runs to ensure all active phase decisions and permissions are reflected accurately.