skills.rest
zhongadamwang
zhongadamwangCOMMUNITY
Explore all skills by this author →
GitHub

github-issue-sync-status

Synchronize local task file states with GitHub issue states.

Updated Mar 15, 2026
Search Tags:#automation#markdown#github#issues#sync#task
One-click install
npx skills add https://github.com/zhongadamwang/pricing-tool --skill github-issue-sync-status
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-issue-sync-status
Source: https://github.com/zhongadamwang/pricing-tool/tree/main/.github/skills/github-issue-sync-status
Command: npx skills add https://github.com/zhongadamwang/pricing-tool --skill github-issue-sync-status

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires requests.

What problem does it solve?

Local task files often drift out of sync with GitHub Issues, causing confusion and manual reconciliation. This skill updates the local State field to reflect GitHub issue states while preserving the original file format and metadata, and it does so in a self-contained way with embedded authentication and conflict-resolution logic.

Core Features & Use Cases

  • Self-contained authentication and configuration embedded in the skill; no external config files required.
  • Maps GitHub issue states (open/closed) to local task states and supports conflict handling strategies (manual, github_wins, local_wins).
  • Preserves Markdown structure, appends Last Synced timestamps, and can add a completion date when transitioning to completed.
  • Dry-run and batch processing support for safe planning and auditing.

Quick Start

Run the sync against a target file or directory to update local task states from GitHub issues.

Frequently Asked Questions about github-issue-sync-status

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

FAQPage Schema
How do I sync local markdown task files with GitHub issues?▼

To sync local markdown task files with GitHub issues, run the tool against your target file or directory to update local states from GitHub while preserving the original file format and metadata.

How does conflict resolution work when syncing GitHub issue states to local tasks?▼

Conflict resolution during sync supports three strategies: manual handling, github_wins to prioritize remote states, and local_wins to keep current local task states unchanged during discrepancies.

Do I need external configuration files to authenticate with GitHub for issue synchronization?▼

No, you do not need external configuration files for GitHub authentication. The tool operates in a self-contained mode with embedded authentication, enabling environments without external dependencies.

Can I preview changes before updating local task states from GitHub issues?▼

Yes, you can preview changes using the dry-run feature, which allows safe planning and auditing of state mappings before batch processing actually modifies your local markdown files.

What happens to my markdown structure when syncing local tasks with GitHub issues?▼

Syncing local tasks with GitHub issues preserves your markdown structure and metadata, appending Last Synced timestamps and adding a completion date when transitioning to a completed state.

Related Skills

Explore More Software Engineering Skills→
zhongadamwangzhongadamwang

github-issue-create-update

Create and update GitHub Issues from local task markdown files.

Community
Advanced
athan-dialathan-dial

verify

Run acceptance checks on deployment plans and update task statuses.

Community
Intermediate
BrennonTWilliamsBrennonTWilliams
7

ll-sync-issues

Synchronize local development issues with GitHub Issues via the GitHub API.

Community
Intermediate
YomiamyYomiamy
16

gen-pr

Generate Markdown PR descriptions from GitHub branch names and issues.

Community
Advanced