agentleFS
Sign inStart free
AnmarHaniAnmarHani/SwarmVault/skills/swarm-migrate/SKILL.md

swarm-migrate

Skill5 starsChanged 4 months agoMITView on GitHub

Bring existing projects into the SwarmVault — register, mirror docs, optionally mine the repo into SDLC artifacts and resume the flow mid-phase (brownfield adoption). Use when the user wants existing projects migrated/connected to the vault, or an existing codebase placed into the SDLC flow.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never re-ask what the repo answers.

    line 40
  2. Distinctive:

    Ask once (if unset): vault as default for new projects?

    line 46

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

swarm-migrate — existing-project migration

Three tiers per project; each deeper tier is opt-in with its cost stated up front. Idempotent: re-running repairs, never duplicates.

1. Discover

List candidates: swarmvault.py register --import-claude covers Claude Code users' ~/.claude.json in one shot; otherwise the user names paths. Ask WHICH projects to migrate (multi-select) and, per project, the isolation flag.

2. Immediate tier (cheap, always)

Per chosen project: register + marker → first sync (mirrors existing CLAUDE.md/AGENTS.md/README/docs and any existing memory; builds the MOC) → wire the platforms they name with setup/wire (as swarm-init step 3; one command, no manual file edits). The project is now queryable.

3. Digest tier (token-costing, opt-in)

State the rough cost first. Analyze the repo → 10 Projects/<P>/<P> Digest.md (architecture, conventions, entry points — not generated, so sync preserves it) + seed memories for footguns found in code comments/READMEs/issue notes.

4. SDLC adoption tier (most token-costing, opt-in) — place it IN the flow

Mine first, ask second (swarm-spec's brownfield mode does the work):

  1. Sources: README, docs/, existing plan/TODO files, issue exports, test suites, the code.
  2. Produce docs/SRS.md + feature specs marked status: mined-draft, every statement with provenance (file:line).
  3. Detect the de-facto phase — e.g. "14 of 20 mined features implemented, no design doc" — and write flow-state accordingly.
  4. Gap interview via the question queue: only gaps, conflicts, low-confidence items. Never re-ask what the repo answers.
  5. Remaining work → tickets. From here /swarm-flow resumes the project mid-phase like any SwarmVault project.

Close

Ask once (if unset): vault as default for new projects? Show the security disclaimer (swarm-init step 4) if this user hasn't seen it. Huge monorepo → scope the deep tiers to user-chosen subpaths. A project containing its own Obsidian vault → exclude that folder from doc mirroring (no vault-in-vault).

Influences: Jeffallan's spec-miner & legacy-modernizer; the original Claude Vault migration — see CREDITS.md.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free