skills.rest
carson-sweet
carson-sweetCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

project-gh-sync-issues

Synchronize issue statuses between local Markdown files and GitHub Issues.

6|3|Updated Apr 12, 2026
Search Tags:#automation#workflow#github#backlog#sync#issue-tracking
One-click install
npx skills add https://github.com/carson-sweet/sweetclaude --skill project-gh-sync-issues
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: project-gh-sync-issues
Source: https://github.com/carson-sweet/sweetclaude/tree/main/skills/project-gh-sync-issues
Command: npx skills add https://github.com/carson-sweet/sweetclaude --skill project-gh-sync-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, python3, pyyaml, and includes scripts (resource) components.

What problem does it solve?

This skill resolves the friction of maintaining two separate sources of truth for project tasks by automating the bidirectional status synchronization between local Markdown issue files and GitHub Issues.

Core Features & Use Cases

  • Automated Status Sync: Automatically closes local issues when the corresponding GitHub issue is closed, and vice versa.
  • Migration Guard: Includes a safety check to prevent data loss or corruption when transitioning from legacy issue formats to the unified taxonomy.
  • Use Case: When a developer marks a task as done in their local project backlog, this skill ensures the corresponding GitHub issue is automatically closed, keeping project stakeholders updated without manual intervention.

Quick Start

Run the project-gh-sync-issues skill to synchronize the status of your local backlog files with your GitHub repository.

Frequently Asked Questions about project-gh-sync-issues

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

FAQPage Schema
How do I sync local issue files with GitHub Issues automatically?▼

GitHub issue sync requires authenticated GitHub CLI access and a configured git remote to perform bidirectional state updates between your local backlog and the repository.

What is the best way to keep local Markdown backlog files in sync with GitHub?▼

This approach operates exclusively on the .sweetclaude/product/backlog/ directory while enforcing strict migration safety guards to prevent data loss or corruption.

Do I need the GitHub CLI to synchronize issue statuses?▼

A configured git remote is also required to perform the bidirectional state updates between your local project backlog and GitHub repository.

Can I sync issues from a custom directory outside the default backlog path?▼

This directory constraint prevents data loss or corruption when transitioning from legacy issue formats to the unified taxonomy.

How does the migration safety guard work when syncing issue statuses?▼

It ensures that local Markdown files and GitHub Issues maintain a consistent single source of truth without overwriting valid state data.

Why does my local issue status not update when I close a GitHub issue?▼

The bidirectional sync requires all three conditions to be met to automatically close local issues when corresponding GitHub issues are closed.

Related Skills

Explore More Software Engineering Skills→
ghbvfghbvf
4

speckit-taskstoissues

Convert design tasks into dependency-ordered GitHub issues linked to design artifacts.

Community
Advanced
aroidoaroido

command-task-done

Automates GitHub issue completion including PRs, checklists, and project board updates using gh, jq, rg.

Official
Advanced
C0ntr0lledCha0sC0ntr0lledCha0s
3

organizing-with-labels

Automate GitHub label and milestone management for issue triage and release planning.

Community
Intermediate
rortan134rortan134
26

to-tickets

Convert plans or specifications into issue tickets with blocking dependencies.

Community
Advanced