agentleFS
Sign inStart free
ryukirinryukirin/openspec-code-migration/skills/migration-setup/SKILL.md

migration-setup

Skill0 starsChanged 35 days agoMITView on GitHub

Install or update the code-migration OpenSpec schema in the current project. Use once per project before migration-inventory, and again after updating these skills.

  • Installs packages

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run openspec --version. If OpenSpec is missing, tell the user to install it (npm install -g @fission-ai/openspec) and stop.

    line 12
  2. Very specific:

    Run openspec list --json. If root is null, the project has no openspec/ directory: ask whether to run openspec init, and do not initialize …

    line 13
  3. Very specific:

    If openspec/config.yaml does not set schema: code-migration, ask whether to make it the project default.

    line 16

≈ “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

Migration Setup

The schema ships with this skill, in the schema/code-migration/ directory next to this file.

  1. Run openspec --version. If OpenSpec is missing, tell the user to install it (npm install -g @fission-ai/openspec) and stop.
  2. Run openspec list --json. If root is null, the project has no openspec/ directory: ask whether to run openspec init, and do not initialize without a yes.
  3. Copy schema/code-migration/ from this skill's directory to openspec/schemas/code-migration/ in the project, replacing the directory as a whole. If it already exists and differs, list the files that would change and ask before replacing.
  4. Run openspec schema validate code-migration.
  5. If openspec/config.yaml does not set schema: code-migration, ask whether to make it the project default. Without it, new changes need --schema code-migration.
  6. The next step is the migration-inventory skill.

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