subscribe
Add a shared guidelines repo (read-scope subscription or write-scope publish target) to the unified repos list.
Best use case
subscribe is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Add a shared guidelines repo (read-scope subscription or write-scope publish target) to the unified repos list.
Teams using subscribe 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/subscribe/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How subscribe Compares
| Feature / Agent | subscribe | 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?
Add a shared guidelines repo (read-scope subscription or write-scope publish target) to the unified repos list.
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
# Subscribe to a Shared Repo
## Overview
Configured guidelines repos are multi-reader / multi-writer git databases,
described in a single unified list in `evolve.config.yaml`:
```yaml
repos:
- name: memory
scope: write
remote: git@github.com:alice/evolve.git
branch: main
notes: public memory for foobar project
- name: org-memory
scope: read
remote: git@github.com:acme/org-memory.git
branch: main
notes: private memory shared only within my org
```
- `scope: read` — download-only. Synced on every run.
- `scope: write` — publish target. Synced on every run too, so you see
what you have already published and anything others have pushed.
## Workflow
### Step 1: Bootstrap config if missing
If `evolve.config.yaml` does not exist, ask the user for a username and
create:
```yaml
identity:
user: {username}
repos: []
sync:
on_session_start: true
```
Also ensure `.evolve/` is gitignored:
```bash
grep -qxF '.evolve/' .gitignore 2>/dev/null || echo '.evolve/' >> .gitignore
```
### Step 2: Gather details
Ask the user for:
- the remote URL for the guidelines repo
- a short local name such as `alice`
- the scope: `read` (default, subscribe-only) or `write` (also a publish target)
- an optional note
### Step 3: Run subscribe script
```bash
python3 ${CLAUDE_PLUGIN_ROOT}/skills/evolve-lite/subscribe/scripts/subscribe.py \
--name "{name}" \
--remote "{remote}" \
--branch main \
--scope "{scope}" \
--notes "{notes}"
```
### Step 4: Confirm
Tell the user the repo was added and they can run `/evolve-lite:sync`
immediately if they want to pull updates now.
## Notes
- The repo is cloned directly into `.evolve/entities/subscribed/{name}/`,
which doubles as the recall mirror
- Subscribed entities will appear in recall with `[from: {name}]`
annotations
- Read-scope repos use a shallow clone; write-scope repos use a full
clone so publish commits can be rebased and pushed cleanlyRelated Skills
unsubscribe
Remove a repo from the unified repos list and delete its local clone.
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.
sync
Pull the latest guidelines from every configured repo (read- and write-scope).
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:sync
Pull the latest guidelines from every configured repo (read- and write-scope).
evolve-lite:save
Captures the current session's successful workflow and saves it as a reusable skill with SKILL.md and helper scripts