You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(bob): port unified scoped repos sharing model from PR #217
Mirror the Claude/Codex changes from #217 in Bob's evolve-lite plugin:
- publish: select a write-scope target via the unified `repos:` list,
write into the write-scope clone at entities/subscribed/{repo}/
guideline/, stamp source from the repo's remote, audit the repo
- subscribe: --scope read|write argument, full clone for write so
publish commits can be rebased and pushed cleanly
- sync: scope-aware (read = fetch + reset --hard, write = fetch +
rebase to preserve unpushed publishes); auto-clone missing repos
- unsubscribe: operate on the unified repos list; SKILL.md warns when
removing a write-scope repo
- recall: drop the obsolete .evolve/public/ source (publishes now
live under subscribed/{repo}/) and skip .git/ paths
Update Bob's command markdowns and README to describe the unified
read/write-scope sharing model, and rewrite test_bob_sharing.py to
match (44 tests passing).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Evolve Lite supports sharing guidelines between users via public Git repositories. You can publish your own guidelines so others can subscribe to them, and subscribe to guidelines published by others.
65
+
Evolve Lite treats shared guidelines as multi-reader / multi-writer git
66
+
databases. A single unified `repos:` list in `evolve.config.yaml`
67
+
describes every external guideline repo; each entry has a `scope` of
68
+
`read` (subscribe only) or `write` (publish target that is also pulled
69
+
on sync).
62
70
63
71
### Setup
64
72
65
-
Sharing requires an `evolve.config.yaml` at the project root. If it doesn't exist, the subscribe or publish skills will prompt you to create one. Minimal structure:
73
+
Sharing requires `evolve.config.yaml` at the project root. If it doesn't
74
+
exist, the subscribe or publish skills will prompt you to create one.
75
+
Minimal structure:
66
76
67
77
```yaml
68
78
identity:
69
79
user: yourname # used to stamp ownership on published guidelines
The `.evolve/` directory is kept out of version control — the skills automatically add it to `.gitignore`.
77
-
78
-
### Publishing Guidelines
79
80
80
-
Use `evolve-lite:publish` to share one or more of your local guidelines with others:
81
-
82
-
1. The skill lists files in `.evolve/entities/guideline/`
83
-
2. You pick which ones to publish
84
-
3. Each selected file is moved to `.evolve/public/guideline/`, stamped with your username as the owner, committed, and pushed to your `public_repo.remote`
description: Subscribe to another user's public guidelines repo
3
+
description: Add a shared guidelines repo (read- or write-scope) to the unified repos list
4
4
---
5
-
Use the subscribe skill to learn from others' guidelines. Follow the skill's instructions exactly.
5
+
Use the subscribe skill to add a shared guidelines repo — either a read-scope subscription or a write-scope publish target. Follow the skill's instructions exactly.
0 commit comments