sync
Pull the latest guidelines from every configured repo (read- and write-scope).
Best use case
sync is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Pull the latest guidelines from every configured repo (read- and write-scope).
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
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/sync/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How sync Compares
| Feature / Agent | sync | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Pull the latest guidelines from every configured repo (read- and write-scope).
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 Repos
## Overview
Pull the latest guidelines from every repo in `evolve.config.yaml`
`repos:` list — both `scope: read` (subscribe-only) and `scope: write`
(publish targets). Write-scope repos use a rebase strategy so any
unpushed local publish commits are preserved.
## Workflow
### Step 1: Run sync script
```bash
python3 ${CLAUDE_PLUGIN_ROOT}/skills/evolve-lite/sync/scripts/sync.py
```
### Step 2: Display summary
Show the script output to the user. If there are no repos configured,
tell them they can add one with `/evolve-lite:subscribe`. If there
are no changes, explain that everything is already up to date.
## Notes
- Read-scope repos are mirrored exactly via `git fetch` + `git reset --hard`
- Write-scope repos use `git fetch` + `git rebase` so unpushed local
publish commits are preserved
- Sync results are logged to `.evolve/audit.log`Related Skills
evolve-lite:sync
Pull the latest guidelines from every configured repo (read- and write-scope).
unsubscribe
Remove a repo from the unified repos list and delete its local clone.
subscribe
Add a shared guidelines repo (read-scope subscription or write-scope publish target) to the unified repos list.
save
Captures the current session's successful workflow and saves it as a reusable skill with SKILL.md and helper scripts
save-trajectory
Save the current conversation as a trajectory JSON file in OpenAI chat completion format for analysis and fine-tuning
recall
Must be used at the start of any non-trivial task involving code changes, debugging, repo exploration, file inspection, or environment/tooling investigation to surface stored guidance before analysis or tool use.
publish
Publish a private guideline to a configured write-scope repo.
provenance
Analyze saved trajectories and recall audit events offline to record whether recalled guidelines influenced completed sessions.
learn
Must be used near the end of any non-trivial turn that produced potentially reusable tools, guidance, errors, workarounds, or workflows, so those lessons are saved for future turns.
evolve-lite:unsubscribe
Remove a repo from the unified repos list and delete its local clone.
evolve-lite:subscribe
Add a shared guidelines repo (read-scope subscription or write-scope publish target) to the unified repos list.
evolve-lite:save
Captures the current session's successful workflow and saves it as a reusable skill with SKILL.md and helper scripts