drupal-migrate

Plugin drupal-migrate from marketplace sf-agents-harness in sparkfabrik/sf-agents-harness. Commands read from the repo's manifest — 5 days ago.

Skills (21)

• drupal-migrate-analysis-docs

  Organize the documentation produced during a Drupal content migration so it stays readable and scoped. Use whenever you are writing up, structuring, or reorganizing migration analysis — "where should this migration doc go", "structure the migration documentation", "document the source site", "the mi

• drupal-migrate-codebase-scan

  Scan the source codebase of a migration into Drupal and classify each custom code unit by disposition — replicate-as-module, replace-with-config, triage (needs a decision), do-not-port, or security (delete + report). Reads custom plugins/modules/themes and loose files to determine what each does and

• drupal-migrate-content-inventory

  Produce the as-is content-inventory document for a migration into Drupal — the content volumes the source holds today. Counts entities per content type / post type (published vs total), measures multilingual coverage, and for a multisite source breaks volume down per site. Use during as-is analysis

• drupal-migrate-count-instances

  Count how many instances of a Drupal entity bundle (node, paragraph, taxonomy term, media, or user) exist in a source migration database, using revision-safe COUNT(DISTINCT) queries that avoid inflation from revisions and language variants. Use only in a migration context, when planning needs a coun

• drupal-migrate-db-discover

  Discover and validate the source database connection for a migration into Drupal. Use after drupal-migrate-detect-source, at the start of any source-database analysis, when a query against the old site's DB fails, or whenever a later drupal-migrate-* step needs to confirm the source DB is reachable.

• drupal-migrate-detect-container

  Detect whether a source paragraph bundle is a group/container that holds child paragraph entities via entity_reference_revisions fields, and list its child bundles. Use before analysing a paragraph''s fields when planning a migration — to discover nested paragraph hierarchies, e.g. "is source paragr

• drupal-migrate-detect-source

  Identify the source system of a migration into Drupal before any analysis — the source technology (WordPress, Drupal 7, Drupal 8+, or another CMS), whether it is single-site or multisite, whether the full codebase is available or only a database dump, and which read-only DB access method to use (dru

• drupal-migrate-detect-version

  Detect whether a Drupal source database is Drupal 7 or Drupal 8+, and the exact core major when the source codebase is available, by checking version-specific table signatures. This is the Drupal-only sub-step of drupal-migrate-detect-source: run it after that skill has established the source is Dru

• drupal-migrate-ecosystem-map

  Produce the as-is ecosystem document for a migration into Drupal — the external systems the source site integrates with today (CRM, mailing, form back-ends, analytics, payment, single sign-on). Captures each integration''s direction, mechanism, and the data that crosses the boundary, with a topology

• drupal-migrate-field-population

  Measure how full each field of a Drupal source bundle actually is: for every field, the share of active instances that hold data, so empty (0%) and near-empty fields can be flagged as non-migration candidates. Use in a migration context only: after drupal-migrate-query-fields, when asked "which fiel

• drupal-migrate-ia-audit

  Produce the as-is information-architecture document for a migration into Drupal — the source site''s structure and URL state today. Captures the navigation menus, the URL/permalink scheme, and the redirect + liveness state (which paths are live, redirected, or gone), and for a multisite source class

• drupal-migrate-live-screenshots

  Take browser screenshots of the live example pages that drupal-migrate-resolve-examples found, so a reviewer sees how a source bundle renders today. Optional step: run only when the user asks for screenshots ("screenshot the example pages", "show me what X looks like on the live site") or the invoca

• drupal-migrate-mapping-triage

  Produce the to-be mapping document that bridges a documented source onto the Drupal target — the triage step between as-is analysis and implementation. Maps each source module/plugin to a Drupal disposition (core / contrib / custom module / drop), maps the source content model onto target content ty

• drupal-migrate-parent-context

  Find where a Drupal source paragraph bundle is embedded: which entity types and fields reference it, which node bundles contain it, and whether it sits in a top-level node field or nested inside another paragraph. Use after drupal-migrate-count-instances when planning a paragraph migration, or when

• drupal-migrate-platform-audit

  Produce the as-is platform document for a migration into Drupal — the source platform exactly as it is today. Captures the CMS version, hosting/PHP/DB engine, single-site vs multisite (with subsite count), the active module/plugin inventory with verified activation state, and the custom-code list. U

• drupal-migrate-query-fields

  Query the field definitions of a source entity bundle from a migration database — base fields plus configurable fields, with label, machine name, type, cardinality, required, and translatable. Use when migration planning needs a bundle''s field list, e.g. "what fields does X have in the source", "li

• drupal-migrate-resolve-examples

  Resolve live URLs for representative example content from a Drupal source database: one published node per parent bundle that uses the bundle under analysis, including paragraphs, terms and media reached through their parent nodes. A required, automatic step in every full bundle analysis. Use when a

• drupal-migrate-scan-destination

  Scan destination Drupal config YAML and project analysis documents to propose source-to-destination field mappings for a migration, and pick the destination bundle/component for a source''s data. Use after querying source fields, when you need to know which destination bundle/fields a source bundle

• drupal-migrate-tech-analysis

  Read a Drupal content-migration issue (GitLab or GitHub, or issue content supplied directly) and produce a precise checkbox TO DO list of the technical tasks needed to implement it, grounded in the project''s actual codebase. Use when the user gives an issue number for a migration — "do a tech analy

• drupal-migrate-verify-active

  Verify active vs orphaned paragraph instances by checking them against the current published revision of their parent nodes. Use after drupal-migrate-parent-context, before sizing a paragraph bundle''s migration scope, when asked "how many of this paragraph are actually in use", or when total DB cou

• drupal-migrate-verify-content

  Verify migrated content by navigating source and destination website pages, comparing content through LLM reasoning, checking HTTP redirects, and validating translations. Use this skill whenever the user asks to "verify migration", "check migrated content", "compare source and destination pages", "v

Subagents (1)

• drupal-migration-analyst

  Full-lifecycle, source-agnostic migration analyst for migrations into Drupal. Orchestrates a content migration through three macro-phases — as-is source analysis, mapping triage, and implementation — by reading the accumulated migration docs to recover prior decisions, running atomic drupal-migrate-

Similar plugins