Issue Fields Migration

Migrates existing metadata into GitHub's new org-level issue fields from two sources: repository labels (like p0/p1 priority tags) and Project V2 custom fields. If you've been using labels as makeshift metadata or have project-specific fields you want to standardize across repos, this walks you through the migration with auto-suggested mappings, conflict detection when multiple labels target the same field, and optional cleanup afterward. GitHub now gives every org preconfigured Priority, Effort, and date fields plus 25 custom slots, so this is basically the bridge from your old workarounds to proper typed metadata. The label-matching logic is smart enough to handle common patterns like prefix-number schemes and case variations, which saves you from manually mapping dozens of labels.

skills.sh installs: 1.9K
GitHub stars: 41K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add github/awesome-copilot --skill issue-fields-migration --agent claude-code

Installs into .claude/skills of the current project.

Files

Issue Fields Migration

Issue fields are org-level typed metadata (single select, text, number, date) that replace label-based workarounds with structured, searchable, cross-repo fields. Every organization gets Priority, Effort, Start date, and Target date preconfigured, with support for up to 25 custom fields.

This skill bulk-migrates existing metadata into issue fields from two sources:

Repo labels: Convert labels like p0, p1, priority/high into structured issue field values (e.g. the Priority field). Supports migrating multiple labels at once and optionally removing them after migration.
Project V2 fields: Copy field values (single select, text, number, date, iteration) from a GitHub Project into the equivalent org-level issue fields.