SkillA skill gives Relay a specialist method it can reuse on your work.Product and engineeringCommunity
Medium riskSecurity review passed

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.

How it works

What issue-fields-migration does

Issue fields are org-level typed metadata (single select, text, number, date) that replace label-based workarounds with structured, searchable, cross-repo fields.

Use it 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.

Inputs and results

What goes in, what comes back

  1. You give

    A short brief describing what you need

    Add a specialist method to the work.

  2. You get

    A finished result to review

    The method guides the work with your files and context.

  3. You check

    The sources and open questions

    Review the output against your brief.

Questions and answers

Questions about issue-fields-migration

Updated May 13, 2026.

What does issue-fields-migration do?

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.

Who is issue-fields-migration for?

It is designed for teams that want to hand off recurring work and review the result before it is used.

What do I need to use it?

Nothing extra is needed. Sign in to Relay to run it with your own files and context.

What does issue-fields-migration produce?

A finished result to review. Results come back with their sources and any open questions for you to check before anything is used.

How much does issue-fields-migration cost?

It is free to use. Paid model usage, if any, is shown before a run.

Can an AI agent use it?

Yes. Agents can read its public definition through the Relay API and run it with a person’s authorization. See the For Agents page for how to connect.

Details

Trust, access and technical details

Trust and access

Visibility
Public: anyone can view
Status
Published and maintained
Pricing
Free
Medium riskSecurity review passedBehavior not evaluated
Reviewed version
cmoq1bgan01n1…
Reviewed
May 13, 2026
Static signals
1 signal
Source provenance
Commit pinned

Security review is a static package assessment, not a guarantee of safety or a behavioral qualification.

Use it from code or an agent

Read the public definition, then check cost and inputs with a preflight before a run.

Open definition

POST /api/v1/runs/preflight

How agents connect to Relay →

Tags and source

Repo
github/awesome-copilot
License
MIT

Connections

Where issue-fields-migration fits

Similar skills5

Skill · Product and engineering

benchmark-optimization-loop

Use when the user asks to make something faster, try many variants, run recursive optimization, benchmark latency/throughput/cost, or choose the best implementation by repeated measured tests.Free
Skill · Marketing

codebase-design

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.Free
Skill · Product and engineering

diagnosing-bugs

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.Free
Skill · Product and engineering

GitNexus Impact Analysis

Assess the likely consequences of a proposed or local code change with GitNexus graph evidence, then verify the result against the exact repository. Use for dependency tracing, blast-radius analysis, regression planning, and deciding whether a shared symbol is safe to change.Free
Skill · Product and engineering

intent-driven-development

Turn ambiguous or high-impact product and engineering changes into scoped, verifiable acceptance criteria before or alongside implementation. Use when a user asks to clarify a feature, define acceptance criteria, de-risk a security/data/migration/integration change, prepare implementation requirements for another agent, or make a complex request testable. Do not trigger for trivial edits, straightforward fixes, active debugging, code review, or implementation requests whose acceptance conditions are already clear unless the user explicitly invokes this skill.Free

Have a task this would help with?

Describe it. Relay plans the work, picks the right playbook and shows the cost before anything runs.

Loading request box