evolve-lite:sync
Pull the latest guidelines from every configured repo (read- and write-scope).
git clone --depth 1 https://github.com/AgentToolkit/altk-evolve /tmp/evolve-lite-sync && cp -r /tmp/evolve-lite-sync/platform-integrations/bob/evolve-lite/skills/evolve-lite-sync ~/.claude/skills/evolve-lite-syncSKILL.md
# 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 .bob/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`
Read all atomic guidelines in wiki-twobatch/guidelines/ and propose themed clusters that group near-duplicates. Writes cluster pages and updates _config.yaml; originals are preserved with a `superseded_by:` backref.
Consult an agent-wiki for guidelines relevant to the task at hand. The wiki itself documents how to retrieve from it (AGENTS.md). Use this skill once you know what task or sub-task you're about to do — not at session start.
Read a normalized Claude Code trajectory JSON and extract reusable guidelines into wiki-twobatch/guidelines/. Use when mining saved trajectories for reusable lessons.
Ingest one or more agent trajectories (raw bob/claude traces or normalized JSON) into an agent-wiki end-to-end — convert, summarize, extract guidelines, synthesize skills, consolidate into clusters, and catalog. Use when you have a batch of traces to turn into a wiki in one pass.
Read a normalized Claude Code trajectory JSON and write an episodic summary page to wiki-twobatch/summaries/. Use when summarizing one or more saved trajectories into the agent wiki.
Read a normalized Claude Code trajectory JSON and produce a wiki-resident SKILL.md page that future agents can invoke. Use when a trajectory captured a non-trivial successful workflow worth promoting from a free-text guideline to an executable, callable artifact.
Discover task families across summaries and write per-family comparison pages with findings narrative. Updates wiki-twobatch/_config.yaml task definitions and writes tasks/<slug>__task.md.
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.