agentsclimarketplace

Generate migration manifest

Skill jeffsenso/prestashop-skills/skills/prestashop-module-development/ps9-core-ai/Component/Migration/skills/generate-migration-manifest

Prestashop Developer Skills

Install
npx -y skills add jeffsenso/prestashop-skills --skill generate-migration-manifest

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

  • 4 stars4 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

Synthesize the outputs of `audit-legacy-controller` and `audit-object-model` into a single `migration-manifest.md` that serves as the migration specification. Every subsequent migration step reads from this document to know what to create.

SKILL.md

2.3 KB, as published. Nobody here has run it

Instructions

  1. Create migration-manifest.md at an agreed location (e.g., docs/migration/{domain}-manifest.md or project root).
  2. Section 1 — Commands: list Add, Edit, Delete, BulkDelete, BulkToggleStatus, ToggleStatus for the domain. Mark each as required or conditional.
  3. Section 2 — Queries: list GetForEditing (returns edit DTO) and GetList (for grid). Note any additional queries (e.g., GetForView).
  4. Section 3 — Form fields: list each field with type, translatable (Y/N), required (Y/N), validation rule. For complex domains only, propose a tab grouping using NavigationTabType — most pages do not need tabs.
  5. Section 4 — Grid columns: list each column with its type (DataColumn, ToggleColumn, ActionColumn, PositionColumn).
  6. Section 5 — Grid filters: list each filter with its type (TextFilter, SelectFilter, DateRangeFilter, etc.).
  7. Section 6 — Sub-resources: list any has-many relations (e.g., carrier ranges, carrier zones) that warrant their own commands and repositories.
  8. Section 7 — Hooks: list all legacy hooks with their Symfony equivalents or note "no equivalent yet".
  9. Section 8 — Milestone decision: based on complexity, propose how to split the migration (e.g., listing first / form later, or single sprint for simple pages).

Rules

  • This document is the single source of truth — all subsequent migration steps must reference it, not the legacy files
  • Every field discovered during the ObjectModel audit must appear in either a form field or a grid column in the manifest
  • Mark sub-resources explicitly — missing a sub-resource here causes silent data loss in handlers
  • The milestone decision is per-page judgment — split listing/form into separate PRs when the entity is complex; a single PR is fine for simple entities

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.