Agent skill · software engineering · github
issue-fields-migration
Bulk-migrate metadata to GitHub issue fields from two sources: repo labels (e.g. priority labels to a Priority field) and Project V2 fields. Use when users say "migrate my labels to issue fields", "migrate project fields to issue fields", "convert labels to issue fields", "copy project field values to issue fields", or ask about adopting issue fields. Issue fields are org-level typed metadata (single select, text, number, date) that replace label-based workarounds with structured, searchable, cross-repo fields.
Why this skill is useful
Adds specific commands and workflows for migrating GitHub issue fields that the AI wouldn't reliably generate on its own.
What it needs
Requires gh installed locally. Requires github account access. About 12k tokens when loaded. Last updated 2026-08-07. 37,534 stars on the source repository.
What this skill does
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. When to Use User added org-level issue fields that overlap with existing project fields User wants to copy values from project fields to issue fields before deleting the old project fields User asks about "migrating", "transferring", or "copying" project field data to issue fields User wants to convert repo labels (e.g., p0, p1, p2, p3) into issue field values (e.g., Priority field) User asks about replacing labels with issue fields or cleaning up labels after adopting issue fields Prerequisites The target org must have issue fields enabled The issue fields must already exist at the org level For project field migration: issue fields must be added to the project For label migration: labels must exist on the target repo(s) The user must have write access to the repos (and project, if migrating project fields) gh CLI must be authenticated with appropriate scopes Available Tools MCP Tools (read operations) Tool Purpose ------ --------- mcpgithubprojectslist List project fields (listprojectfields), list project items with values (listprojectitems) mcpgithubprojectsget Get details of a specific project field or item CLI / REST API Operation Command ----------- --------- List org issue fields gh api /orgs/{org}/issue-fields -H "X-GitHub-Ap …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills github/issue-fields-migration