sync-from-repos

Sync from reference repos

Scan reference repositories, compare against plugin skills/agents/commands, and recommend improvements. Read-only analysis — no changes without explicit approval.

Configuration

REPOS_DIR=~/ai/repos
PLUGIN_DIR=plugins/whetstone
SYNC_LOG=docs/audit/audit-log.md

Phase 0: Pre-flight — read prior decision log

Read $SYNC_LOG in full before any analysis. Two things come out of it.

First, the Retired sources table above the ## Log marker: repos exhausted by a prior run, each pinned to the HEAD SHA it was retired at. Carry it into Phase 2, which defines the check and the un-retire rule.

Second, build an in-memory set of already-evaluated findings keyed by (component, pattern-signature) across every run entry. Use it as a filter during Phase 3 and Phase 4:

• Previously applied, exact match — drop silently.
• Previously rejected, exact match — drop silently unless new evidence contradicts the prior reason; if so, surface with a RE-EVALUATE flag and quote the prior rejection reason.
• Previously deferred, exact match — surface with a PREVIOUSLY DEFERRED tag and the original defer reason so the user can judge whether conditions have changed.
• No match — present normally.

While reading, also detect prune triggers. These three buckets match /prune-sync-log's taxonomy exactly (a missing external repo is a stale-ref, not its own bucket). Emit a one-line reminder at the end of Phase 4 if any fire:

• age — any entry older than 30 days.
• stale-ref — any entry referencing a component that no longer exists under $PLUGIN_DIR (skill, agent, or command path missing), OR an external repo no longer present in $REPOS_DIR.
• superseded — any entry whose rejection reason duplicates a rule now in MEMORY.md.

Reminder format: "Sync log has N prune candidates (age: X, stale-ref: Y, superseded: Z) — run /prune-sync-log."

If $SYNC_LOG doesn't exist, note it and continue — the post-apply step in Phase 5b creates it.