com um clique
migrate-docs-project-man
View and update the documentation migration tracker
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Menu
View and update the documentation migration tracker
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
| name | migrate-docs-project-man |
| description | View and update the documentation migration tracker |
| argument-hint | [update|add|audit|banners] [options] |
Manage the documentation migration tracker at MIGRATION_TRACKER.md in the repository root.
Arguments: $ARGUMENTS
Parse $ARGUMENTS to determine the action. If no arguments are provided, default to display.
MIGRATION_TRACKER.md at the repository root.redirect-needed or deprecation-needed bannersto-migrate pagesupdate <legacy-path> <field>=<value> [<field>=<value> ...])Update a specific entry in the tracker.
MIGRATION_TRACKER.md.<legacy-path> in the detailed tables.migration=<migrated|to-migrate|deprecate|skip>location=<path> (new location in docs-public)banner=<none|redirect-needed|redirect-added|deprecation-needed|deprecation-added|removed>notes=<text>Last updated date to today.add <legacy-path> --status=<status> --category=<category> [--notes=<text>])Add a new legacy page entry to the tracker.
MIGRATION_TRACKER.md.<legacy-path>).<status> (default: to-migrate)-none<text> if providedLast updated date.audit)Cross-check the tracker against the codebase for inconsistencies.
MIGRATION_TRACKER.md..md files under docs-public/docs/ for <!-- TODO: update link when migrated --> comments.migrated in the tracker? If so, flag it as TODO comment should be removed (the link should be updated to the new local path).skip? If so, flag the TODO comment as incorrect (skip pages don't get migrated, so the TODO is misleading).CLAUDE.md against the tracker:
migrated row in the tracker.migrated row in the tracker should have a corresponding entry in CLAUDE.md.banners)Show all pages that need manual banner action on the legacy site.
Read MIGRATION_TRACKER.md.
Collect all rows where Legacy Banner is redirect-needed or deprecation-needed.
Display them grouped by type:
Redirect banners needed (migrated pages): List each legacy path with its new location, so the user knows what URL to put in the banner.
Deprecation banners needed (deprecated pages): List each legacy path with its notes.
Provide a count summary: "X redirect banners and Y deprecation banners need to be added."
When recalculating (used by update, add, and audit actions):
Migrated = total rows with migratedRedirect banner needed = total rows with redirect-neededRedirect banner added = total rows with redirect-addedLegacy page removed = total rows with banner removedTo migrate = total rows with to-migrateTo deprecate = total rows with deprecateSkip (service/MPEC/data) = total rows with skipLast updated date.