Sync Merged PR ↔ Issue Tracker

Maintenance skill. Walk a window of recent pull requests; where a PR authoritatively closes an issue, close the issue with a linked comment; where a PR was closed without merge and claimed to fix an issue, leave an informational comment on the issue instead of closing it. Never act on bare #N mentions — only on authoritative close links.

When to use

• Before tagging a release, to flush stale "fixed" issues.
• After a batch merge day, to reconcile the tracker.
• On a recurring schedule (a cron job or a scheduled agent run).

Arguments

• --since <value> (optional) — lower bound for mergedAt / closedAt. Accepts an ISO date (2026-04-01), a git ref (v0.4.10), or the literal last-release. Default: last-release → resolve to the most recent release heading date in CHANGELOG.md (e.g. # X.Y.Z (YYYY-MM-DD)); if that cannot be parsed, fall back to the last 7 days.
• --limit <n> (optional) — maximum number of PRs to process. Default: 100.
• --dry-run (optional) — print planned mutations but do not post comments or close issues.
• --repo <owner>/<name> (optional) — override repo detection. Default: inferred from gh repo view --json nameWithOwner.

Workflow