publish

Publish an Entity

Overview

Publish one or more private entities from .evolve/entities/<type>/ into a configured write-scope repo. <type> is the directory the entity was saved in: guideline for learned guidelines, or a native memory type (user, feedback, project, reference) for entities saved by adapt-memory or the EVOLVE.md save flow. The entity is stamped with visibility: public, owner, published_at, and source, moved into the local clone of the write repo under the same <type>/ directory, and committed / pushed to the remote.

The same local clone is also what /evolve-lite:sync pulls from — so you and anyone else publishing to the same repo stay in sync.

Workflow

Step 1: Require a write-scope repo

Read evolve.config.yaml. If no entry has scope: write, tell the user:

"You need at least one write-scope repo to publish to. Run /evolve-lite:subscribe with --scope write to set one up, then come back."

Then stop.

If identity.user is missing, ask for it and add it to the config.

Step 2: First-time setup

Ensure .evolve/ is gitignored at the project root:

grep -qxF '.evolve/' .gitignore 2>/dev/null || echo '.evolve/' >> .gitignore

Step 3: Pick the target write-scope repo

Filter repos: to entries with scope: write (Step 1 already aborted if there were zero, so at least one exists here).

• Exactly one entry → use it as default.
• Multiple entries → show a numbered list with notes and ask which to publish to.

Let {repo} be the chosen repo name and {branch} its configured branch (default main).

Step 4: List and select entities

List the .md files in every type directory under .evolve/entities/, skipping .evolve/entities/subscribed/ (other people's entities, never yours to publish). Show each as {type}/{filename} and ask the user which to publish.

Step 5: Run publish script

For each selected file, run:

python3 ${CLAUDE_PLUGIN_ROOT}/skills/evolve-lite/publish/scripts/publish.py \
  --entity "{filename}" \
  --type "{type}" \
  --repo "{repo}" \
  --user "{identity.user}"