auto-sync

Synchronizes SPEC status, changelogs, and project documentation after implementation completes.

111|73|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/autopus-ai/autopus-adk --skill auto-sync-autopus-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: auto-sync
Source: https://github.com/autopus-ai/autopus-adk/tree/main/.omp/skills/auto-sync
Command: npx skills add https://github.com/autopus-ai/autopus-adk --skill auto-sync-autopus-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After code is implemented, project documentation often drifts out of sync with reality. This Skill closes the gap by updating SPEC statuses, changelogs, architecture docs, and decision records so the repository always reflects the current state of the codebase. ## Core Features & Use Cases - Documentation Synchronization: Marks SPECs as completed, refreshes API docs, architecture diagrams, and CHANGELOG entries after implementation. - @AX Tag Lifecycle Management: Tracks TODO cycle counters, verifies ANCHOR fan-in reference counts, and removes orphaned NOTE tags across the codebase. - Two-Phase Lore Commits: Splits commits between module repositories and the meta repository with conventional commit messages. - Use Case: After finishing a feature with /auto go, run the sync step to mark SPEC-AUTH-001 completed, update ARCHITECTURE.md, record decisions in Lore, and commit everything in the correct repos. ## Quick Start Ask the agent to run /auto sync SPEC-AUTH-001 to synchronize all project documentation and commit the changes.

Frequently Asked Questions about auto-sync

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

FAQPage Schema
How do I sync documentation after implementing a feature?▼

Run /auto sync with a SPEC-ID to update the SPEC status to completed, refresh API docs and architecture diagrams, record decisions in Lore, and update the CHANGELOG. Running it without an ID syncs general project documentation.

What does the auto-sync skill update in a repository?▼

It updates SPEC status, API documentation, architecture diagrams, Lore decision records, and the CHANGELOG. It also refreshes structure documents like ARCHITECTURE.md, structure.md, tech.md, product.md, and workspace.md when structural changes are detected.

How does @AX tag lifecycle management work?▼

The skill increments @AX:CYCLE counters on TODO tags and promotes them to @AX:WARN after three cycles. It verifies @AX:ANCHOR tags have at least three callers, demotes weak anchors to @AX:NOTE, and removes NOTE tags referencing deleted functions.

Why does sync refuse to mark a SPEC as completed?▼

Sync blocks completion when the Completion Verdict shows unresolved Completion Debt, unmet mandatory requirements, or failed Must acceptance criteria. It records a blocked reason instead of changing the SPEC status.

Can auto-sync commit changes across multiple repositories?▼

Yes, it uses a two-phase commit strategy. Changes inside the target module directory are committed to the module repo, while root documents like ARCHITECTURE.md and CHANGELOG.md are committed separately to the meta repository.