agentsclimarketplace

Speckit.migrate

Skill wedabro/bro-skills/.agents/skills/speckit.migrate

bro-skills - Spec-Driven Development CLI

Install
npx -y skills add wedabro/bro-skills --skill speckit.migrate

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Legacy Code Migrator - Reverse-engineer existing codebase to SDD standard.

SKILL.md

1.2 KB, as published. Nobody here has run it

🎯 Mission

Scan legacy codebase → create spec + preliminary plan → evaluate tech debt → propose migration path.

📥 Input

  • Existing codebase (source code, configs, DB schema)
  • .agent/memory/constitution.md (target standards)

📋 Protocol

  1. Scan Phase: Use ProjectScanner patterns to detect:
    • Languages, frameworks, dependencies
    • Data models (Prisma/SQL/Mongoose schemas)
    • API routes, pages, components
    • Docker setup (if any)
  2. Reverse-Engineer Spec: From code → create draft spec.md :
    • Each page/route → 1 User Scenario
    • Each data model → 1 entity description
  3. Tech Debt Inventory (migration-risk.md):
    • 🔴 Critical: Security holes, deprecated deps, no tests
    • 🟡 Important: Missing Docker, no CI/CD, inconsistent patterns
    • 🟢 Minor: Code style, naming conventions
  4. Migration Sequence: Suggested migration order (less risk first).

📤 Output

  • .agent/specs/migration/spec.md (draft)
  • .agent/specs/migration/migration-risk.md

🚫 Guard Rails

  • DO NOT refactor code in this step — just analyze and document.
  • DO NOT delete old code.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.