sync

Fast save-point: sync all session-context files and MEMORY.md with current progress. Zero questions, zero delay. Use when user says /sync, save progress, save state, sync context, or /sync --full for capability inventory.

16 stars

Best use case

sync is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Fast save-point: sync all session-context files and MEMORY.md with current progress. Zero questions, zero delay. Use when user says /sync, save progress, save state, sync context, or /sync --full for capability inventory.

Teams using sync should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/sync/SKILL.md --create-dirs "https://raw.githubusercontent.com/diegosouzapw/awesome-omni-skill/main/skills/development/sync/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/sync/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How sync Compares

Feature / AgentsyncStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Fast save-point: sync all session-context files and MEMORY.md with current progress. Zero questions, zero delay. Use when user says /sync, save progress, save state, sync context, or /sync --full for capability inventory.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Sync

> Zero questions. Edit files. Print summary. Done.

## Rules

1. **No questions** — never ask the user anything. Just save.
2. **No subagents** — run entirely in the main thread.
3. **No MCP tools** — direct file reads and edits only (faster).
4. **No narration** — don't announce steps. Just do them.
5. **Touch every file** — even if only adding a timestamp entry.
6. **Speed over perfection** — a rough sync beats no sync.

---

## Execute

Use the current time formatted as `HH:MM DD/MM/YY` for the checkpoint header.

### 1. Edit `session-context/CLAUDE-activeContext.md`

Append a new section at the end:

```markdown
## [SYNC] {time}

**Accomplished:**
- {bullet list of what was done this session}

**In progress:**
- {what's currently being worked on}

**Next steps:**
- {what comes next}

**Blockers:**
- {any blockers, or "None"}
```

### 2. Edit `session-context/CLAUDE-decisions.md`

Append new decisions made this session. If none, append:

```markdown
## {time}
No new decisions this session.
```

### 3. Edit `session-context/CLAUDE-patterns.md`

Append new patterns discovered. If none, append:

```markdown
## {time}
No new patterns this session.
```

### 4. Edit `session-context/CLAUDE-troubleshooting.md`

Append new issues and solutions. If none, append:

```markdown
## {time}
No new issues this session.
```

### 5. Update MEMORY.md

Update the auto-memory file at the project memory path with any new learnings from this session. If nothing new, skip this file (memory should stay concise).

### 6. Print summary

Print exactly one block:

```
Synced. {N} files updated.
- Active context: {1-line summary of what was captured}
- Decisions: {count new or "no new"}
- Patterns: {count new or "no new"}
- Troubleshooting: {count new or "no new"}
- Memory: {updated or "no changes"}
```

---

## /sync --full (Capability Inventory)

> Extended sync that includes capability inventory generation.

### Execute

1. Run standard sync flow (Steps 1-5 above).
2. Call `session_capability_inventory(project_dir, force_refresh=True)` — bypasses cache and regenerates inventory even if git unchanged.
3. If `needs_generation == True`: the MCP tool will generate the inventory.
4. Read `CLAUDE-capability-inventory.md` if it exists.

### Print summary

Print the standard sync block above, plus:

```
Capability Inventory: {status}
- MCP Tools: {count}
- Test Coverage: {percentage}
- Critical Untested: {count}
- Inventory: {path}
```

Related Skills

sync-docs

16
from diegosouzapw/awesome-omni-skill

Strategic documentation sync - review docs before implementation (pull context) OR export learnings after implementation (push to living docs). NOT bidirectional - two separate one-way operations at different phases.

skill-sync-checker

16
from diegosouzapw/awesome-omni-skill

Detects content drift between skill files and their source documents. Helps maintain skills that are derived from other documentation by comparing content and flagging outdated sections.

openclaw-docs-sync

16
from diegosouzapw/awesome-omni-skill

Sync OpenClaw + ClawHub + Skills docs into a local mirror for the QMD memory backend.

docs-sync

16
from diegosouzapw/awesome-omni-skill

Sync AILANG documentation website with codebase reality. Use after releases, when features are implemented, or when website accuracy is questioned. Checks design docs vs website, validates examples, updates feature status.

async

16
from diegosouzapw/awesome-omni-skill

Regel 10: Async-First mit Symfony Messenger. Use when working with async.

synchronization

16
from diegosouzapw/awesome-omni-skill

Convergence to common trajectory in coupled systems

sync-specs

16
from diegosouzapw/awesome-omni-skill

Sync ALL increment specifications to living docs structure by default. Creates FS-XXX folders for each increment. Use with increment ID to sync single increment.

asyncredux-error-handling

16
from diegosouzapw/awesome-omni-skill

Implement comprehensive error handling for actions. Covers the `wrapError()` method for action-level error wrapping, GlobalWrapError for app-wide error transformation, ErrorObserver for logging/monitoring, and the error handling flow (before → reduce → after).

ado-sync

16
from diegosouzapw/awesome-omni-skill

Help and guidance for Azure DevOps synchronization with SpecWeave increments. Use when asking how to set up ADO sync, configure credentials, or troubleshoot integration issues. For actual syncing, use /sw-ado:sync command.

sync-db

16
from diegosouzapw/awesome-omni-skill

This skill should be used when the user asks to "sync database", "get production data", "download prod db", "migrate database", "update local db", "refresh dev database", or needs to sync production data to local/dev environment.

Skill Synchronizer

16
from diegosouzapw/awesome-omni-skill

Lee los metadatos de todas las skills y actualiza el índice en AGENTS.md.

rust-async-patterns

16
from diegosouzapw/awesome-omni-skill

Master Rust async programming with Tokio, async traits, error handling, and concurrent patterns. Use when building async Rust applications, implementing concurrent systems, or debugging async code.