Skip to content
Back to skills

Sync

ASecurity

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.

  • 88 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added May 26, 2026
toolsgit

Works with

  • mcp

Security analysis

A100/100

Scanned May 27, 2026

npx -y skills add anombyte93/atlas-session-lifecycle --skill sync --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Sync?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Sync
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/anombyte93-sync/badge)](https://www.skillsdirectory.com/skills/anombyte93-sync)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: sync
description: "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."
user-invocable: true
---

# 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}
```

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.