github-sync

Name: github-sync
Availability: InStock
Author: TinNguyen

Synchronize GitHub PRs and issues with the Claude Code task list.

1|Updated Jan 26, 2026

Search Tags:#automation #github #orchestration #issues #sync #pr #task-list

Ready to run

npx skills add https://github.com/AskTinNguyen/vesper-team-skills --skill github-sync-asktinnguyen

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: github-sync
Source: https://github.com/AskTinNguyen/vesper-team-skills/tree/main/github-sync
Command: npx skills add https://github.com/AskTinNguyen/vesper-team-skills --skill github-sync-asktinnguyen

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, bun, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill synchronizes GitHub PRs and issues with the Claude Code task list, enabling teams to coordinate multi-agent workflows around real repository state.

Core Features & Use Cases

Sync open PRs and issues into the Claude Code task list with deduplication by PR/Issue number.
Update task statuses based on PR state (merged, closed) and review outcomes, and reconcile discrepancies across systems.
Ideal for multi-repo automation, governance, and release planning where GitHub artifacts map to concrete tasks.

Quick Start

Run reconcile.sh to perform a full bidirectional sync between GitHub and the Claude Code task list.

Frequently Asked Questions about github-sync

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I sync GitHub PRs and issues with a local task list?▼

Sync GitHub PRs and issues by running a bidirectional reconciliation script that uses gh CLI to fetch repository state and updates task statuses based on PR merge states and review outcomes.

What is GitHub issue and PR synchronization for multi-agent orchestration?▼

GitHub issue and PR synchronization maps open repository artifacts to actionable local tasks, enabling multiple agents to coordinate workflows around real repository state across multiple repositories.

Do I need gh CLI to synchronize GitHub issues and pull requests?▼

Yes, you need the gh CLI installed to authenticate and query GitHub repositories, alongside the bun runtime to execute the synchronization scripts that process local task list metadata.

How does task deduplication work when syncing GitHub issues?▼

Task deduplication works by tracking pr_number and issue_number metadata locally, preventing duplicate task creation when the synchronization script fetches already tracked open PRs and issues from GitHub.

Can I use this for multi-repo GitHub automation and release planning?▼

Yes, this approach is ideal for multi-repo automation and release planning where GitHub artifacts map to concrete tasks, reconciling discrepancies across systems during governance workflows.

Why are my synced GitHub tasks showing discrepancies with repository state?▼

Discrepancies occur when local task statuses fall behind real GitHub PR states; running a full bidirectional sync reconciles these differences by updating tasks according to merged or closed statuses.