meta-mcp: Skill for Claude Code

Fix GitHub Issue(s)

You are fixing GitHub issue(s) $ARGUMENTS in the meta-mcp project.

Parse the arguments: split $ARGUMENTS by spaces, commas, or other separators. Each token may be a bare number (42), a hash-prefixed number (#42), or a full GitHub issue URL. Extract all issue numbers into a list. If no argument is provided, ask the user for the issue number(s).

Single vs. multi-issue mode: if there is only one issue, follow the standard single-issue flow below. If there are multiple issues, follow the multi-issue adaptations noted in each step — all issues are fixed together in one branch, one combined PR.

This workflow works best with extended thinking enabled — complex issues benefit from deep reasoning about root causes and fix strategies.

Step 1: Gather Context

Create tasks to track progress throughout this workflow.

1. Switch to main and update — always start from the latest main:

   git checkout main
   git pull
   

2. Fetch the issue(s) via gh issue view <number> --json title,body,labels,state,milestone — run for each issue number.
3. Read all issues carefully — understand each problem, affected files, severity, and any proposed solutions. In multi-issue mode, note overlaps and shared affected areas.
4. Check if already fixed — for each issue, before exploring code, read CHANGELOG.md (especially the [Unreleased] section and recent releases) and search for references to the issue number (#<number>) or related keywords. When working through a large backlog of issues, earlier fixes may have already resolved or partially addressed some issues. If an issue is already fixed, drop it from the list and inform the user. If ALL issues are already fixed, close the workflow early.
5. Explore the codebase — read the files mentioned across all issues. Use the Grep and Glob tools (not bash grep/find) to search efficiently.
6. Verify with official documentation — if any issue references or implies external APIs, specs, or platform behavior (e.g., anything about Instagram API, Threads API, Meta Graph API), proactively look up the official documentation using WebSearch / WebFetch. Don't wait for the issue to provide links — if the fix touches API endpoints, parameters, or platform-specific behavior, always verify against the source of truth.
7. Check compatibility (multi-issue only) — if two issues propose conflicting changes to the same code, flag this to the user via AskUserQuestion and suggest splitting them into separate PRs.
8. Summarize findings to the user: for each issue — what's broken, what the fix should look like, and what files need changes. In multi-issue mode, highlight shared files and any interactions between fixes.