- name
SKILL.md
स्किल फ़ाइल पब्लिशर की रिपॉज़िटरी में ही रहती है।
कॉपी की गई कमांड टर्मिनल में पेस्ट करें। यह इस SKILL.md को उस एजेंट में इंस्टॉल करती है।
npx skills add glebis/claude-skills --skill cms-migration-checklist -a cursor -yकॉपी की गई कमांड टर्मिनल में पेस्ट करें। यह इस SKILL.md को उस एजेंट में इंस्टॉल करती है।
npx skills add glebis/claude-skills --skill cms-migration-checklist -a claude-code -yकॉपी की गई कमांड टर्मिनल में पेस्ट करें। यह इस SKILL.md को उस एजेंट में इंस्टॉल करती है।
npx skills add glebis/claude-skills --skill cms-migration-checklist -a codex -yकॉपी की गई कमांड टर्मिनल में पेस्ट करें। यह इस SKILL.md को उस एजेंट में इंस्टॉल करती है।
npx skills add glebis/claude-skills --skill cms-migration-checklist -a grok -yकॉपी किया गया संदेश Grok Bot चैट में भेजें। Bot यह SKILL.md GitHub से लाता है और उसे उन स्किल में जोड़ देता है जो आपके सभी Bot साझा करते हैं।
Install this skill: https://github.com/glebis/claude-skills/tree/HEAD/cms-migration-checklistपब्लिशर से
A migration is done when every source record has an accounted outcome, every public URL still answers, editors can publish without WordPress, and you can roll back. A site that merely looks right can still be missing records, URLs or editorial flows, which is why the checklist is split into phases that each end in a gate with evidence.
Don't paste the whole checklist back at the user. Instead:
references/setup.md:
at most 10 questions via AskUserQuestion (the old site's URL or code, how much should
change, URLs, body format, editorial features, plugins, hosting, audience, freeze,
approver), a read-only look at the old site between rounds, and a MIGRATION-BRIEF.md
that marks n/a items and pre-fills the decision packet.MIGRATION-CHECKLIST.md or as tracker epics whose acceptance criteria are the
checklist lines, so the evidence accumulates where the work happens.Read references/pitfalls.md before the audit, conversion, import and deploy phases: it
lists concrete traps with fixes. Read references/cutover-runbook.md when planning the
cutover. Several pitfalls are tied to specific Payload/Next/nginx versions; confirm them
against current docs when the project uses different versions.
SELECT/SHOW/DESCRIBE/WITH/EXPLAIN. Mistakes on a copy are
free; on production they're incidents.db_version, not assumed.post_author; extra roles (translator, photographer) checked against body text.
Public author profiles are not login users, and password hashes don't migrate./page/N/), feeds
(/feed/, per-category feeds), date archives, attachment pages and search. Note slug
collisions across types and existing redirects (Redirection plugin,
_wp_old_slug, framework config), and check that redirect targets exist.Decisions the packet usually needs: hosting · author profiles vs logins · byline order and fallback · extra credit roles · comments (native, read-only archive, third party, or dropped; approved only; spam and unmoderated stay in the source archive; close on old posts?) · donations or other personal data (usually not imported) · editorial workflow (drafts, stages, scheduled publishing) · fields to retire · analytics and Search Console · body format (convert to Lexical, or keep legacy HTML) · admin URL and language.
Gate 0: field matrix, screen map and author mapping reviewed; decision packet answered.
Gate 1: the owner accepts the editor workflow; unsupported features are listed with how each will be handled.
conversionStatus (clean / lossy). Lossy documents go to a manual review list.<img>).Gate 3: reconciliation clean, lossy list reviewed, full URL crawl passes locally.
/api and the admin path alone./wp-content/uploads/... URLs 301 to the imported files (relative
Location); a missing file returns 404, not 500.og:image is an absolute URL on the production host (checked in rendered HTML);
favicon, share images and titles from the starter template replaced.lang,
main landmark, visible focus.X-Forwarded-For.payload migrate run in the deploy.noindex, so search engines don't index a
duplicate of the site.pg_dump matching the server's major version.Gate 6: staging crawl N/N, restore drill passed, off-server backups landing.
Follow references/cutover-runbook.md. In short:
http, www and
old hostnames 301 to the canonical origin, keeping path and query.Gated checklist and working method for migrating a WordPress site to Next.js with a Payload CMS admin — audit, owner decisions, HTML→Lexical conversion, idempotent import and reconciliation, URL/SEO p
---name: cms-migration-checklistdescription: Gated checklist and working method for migrating a WordPress site to Next.js with a Payload CMS admin — audit…---# cms-migration-checklist/SKILL.mdओवरव्यू
Gated checklist and working method for migrating a WordPress site to Next.js with a Payload CMS admin — audit, owner decisions, HTML→Lexical conversion, idempotent import and reconciliation, URL/SEO parity, editorial admin, security probes, self-hosted deploy, DNS cutover, rollback and the first week after. Use this whenever someone is planning, building, reviewing or launching a WordPress → Payload (or WordPress → headless Next.js) migration, even if they only ask one slice of it. Includes a setup mode that interviews the user about the old site and goals and writes a migration brief — "set up a migration for example.com", "are we ready to cut over?", "how do I know the import didn't lose anything?", "what should I audit in the WP database first?", "replace wp-admin with Payload", "move off WordPress", "migration plan for our blog", "will old URLs still work?".
FAQ
पब्लिशर से cms-migration-checklist/SKILL.md डाउनलोड करें, या पाथ कॉपी करके रिपॉज़िटरी खोलें। PlugMCP स्किल को सूचीबद्ध करता है, फ़ाइल होस्ट नहीं करता।
पब्लिशर इसे https://github.com/glebis/claude-skills पर रखता है।
Claude, Cursor, Codex और Grok Build वह SKILL.md पढ़ सकते हैं जिसे आप पब्लिशर की रिपॉज़िटरी से जोड़ते हैं। जब आप चैट में स्किल के GitHub फ़ोल्डर का लिंक भेजते हैं, तो Grok Bot उसे इंस्टॉल कर देता है।