migration-pr-review

Assess migration PRs against a fixed rubric for HTML table parity.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/obaDev95/myf-agent-skills --skill migration-pr-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migration-pr-review
Source: https://github.com/obaDev95/myf-agent-skills/tree/main/skills/migration-pr-review
Command: npx skills add https://github.com/obaDev95/myf-agent-skills --skill migration-pr-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides reviewers to validate migration PRs for HTML table components against a fixed rubric, ensuring parity with legacy behavior, correct DOM and data-attributes, shared SCSS usage, and comprehensive tests and docs.

Core Features & Use Cases

  • Structured review workflow: load the legacy baseline, select the applicable variant, apply the migration rubric, and classify findings as block / follow-up / nitpick.
  • Parity and audit checks: verify logic preservation, DOM structure, data attributes, shared styles, and test coverage against the legacy implementation.
  • Practitioner-focused outputs: generate a concise PR summary with cited baselines and a section-by-section parity assessment for reviews.

Quick Start

Diff the migration PR against the legacy baseline and apply the Variant checklist to identify parity gaps.

Frequently Asked Questions about migration-pr-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review an HTML table migration PR for legacy behavior parity?

To review an HTML table migration PR for parity, diff it against the legacy baseline, apply a variant-specific rubric, and verify logic, DOM structure, data attributes, and shared SCSS styles.

What checks are needed when migrating HTML table components to ensure parity?

Migration parity requires verifying logic preservation, DOM structure, data attributes, shared styles, and comprehensive test coverage against the legacy implementation baseline.

How do I classify findings during an HTML table migration review?

During an HTML table migration review, classify findings into block, follow-up, or nitpick categories based on the severity of parity gaps against the legacy baseline.

Does HTML table migration review require a legacy baseline to verify styles and tests?

Yes, HTML table migration review requires loading the legacy baseline to accurately verify shared SCSS usage, data attributes, and test coverage during the PR assessment.

What should a PR summary include for an HTML table migration review?

A migration PR summary should include cited baselines and a section-by-section parity assessment detailing any logic, DOM, style, or test coverage gaps found.

When should I use a structured rubric for HTML table migration and bug triage?

Use a structured rubric for HTML table migration, regressions, and bug triage when you need to validate exact parity with legacy behavior, styles, and tests.