migrate GitHub issues from one repository to another
72%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./.github/skills/migrate-issues/SKILL.mdUse this prompt when migrating issues from one GitHub repository to another (e.g., from microsoft/vscode-copilot to microsoft/vscode).
You can specify which issues to migrate using any of these three methods:
Provide a full GitHub issues search URL. All matching issues will be migrated.
https://github.com/microsoft/vscode-copilot/issues?q=is%3Aissue+is%3Aopen+assignee%3AyoyokrazyProvide search query syntax for a specific repo. All matching issues will be migrated.
repo:microsoft/vscode-copilot is:issue is:open assignee:yoyokrazyCommon query filters:
is:issue / is:pr - Filter by typeis:open / is:closed - Filter by stateassignee:USERNAME - Filter by assigneeauthor:USERNAME - Filter by authorlabel:LABEL - Filter by labelmilestone:MILESTONE - Filter by milestoneProvide a direct link to a single issue. Only this issue will be migrated.
https://github.com/microsoft/vscode-copilot/issues/12345Target Repository: {TARGET_REPO}
Based on the input provided, migrate the issue(s) to the target repository following all requirements below.
Create the new issue with this header format:
_Transferred from {SOURCE_REPO}#{ORIGINAL_ISSUE_NUMBER}_
_Original author: `@{ORIGINAL_AUTHOR}`_
---
{ORIGINAL_ISSUE_BODY}For each comment on the original issue, add a comment to the new issue:
_`@{COMMENT_AUTHOR}` commented:_
---
{COMMENT_BODY}ALL @username mentions MUST be wrapped in backticks to prevent GitHub from sending notifications.
✅ Correct: `@username`
❌ Wrong: @username
This applies to:
@mentions within the issue body content@mentions within comment content@mentionsIssue references like #12345 are REPO-SPECIFIC. If you copy #12345 from the source repo to the target repo, it will incorrectly link to issue 12345 in the target repo instead of the source.
Convert ALL #NUMBER references to full URLs:
✅ Correct: https://github.com/microsoft/vscode-copilot/issues/12345
✅ Also OK: microsoft/vscode-copilot#12345
❌ Wrong: #12345 (will link to wrong repo)
This applies to:
#12345 → full URL)#12345 → full URL)Exception: References that are already full URLs should be left unchanged.
After creating the new issue and all comments:
Migrated to {TARGET_REPO}#{NEW_ISSUE_NUMBER}microsoft/vscode-copilot):I noticed @johndoe had a similar issue in #9999. cc @janedoe for visibility.
Related to #8888 and microsoft/vscode#12345.
Steps to reproduce:
1. Open VS Code
2. ...microsoft/vscode):_Transferred from microsoft/vscode-copilot#12345_
_Original author: `@originalauthor`_
---
I noticed `@johndoe` had a similar issue in https://github.com/microsoft/vscode-copilot/issues/9999. cc `@janedoe` for visibility.
Related to https://github.com/microsoft/vscode-copilot/issues/8888 and microsoft/vscode#12345.
Steps to reproduce:
1. Open VS Code
2. ...Note: The microsoft/vscode#12345 reference was already a cross-repo link, so it stays unchanged.
@mentions are wrapped in backticks#NUMBER references are converted to full URLsmicrosoft/vscode
278203b
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.