sync-issues

Synchronize GitHub issues with a local Markdown TODO file.

Updated Feb 2, 2026
One-click install
npx skills add https://github.com/har1101/marp-agent-har1101 --skill sync-issues
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync-issues
Source: https://github.com/har1101/marp-agent-har1101/tree/main/.claude/skills/sync-issues
Command: npx skills add https://github.com/har1101/marp-agent-har1101 --skill sync-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the synchronization between GitHub issues and a local docs/TODO.md file, ensuring that your project's task tracking is always up-to-date across both platforms.

Core Features & Use Cases

  • Bi-directional Sync: Automatically adds new GitHub issues to docs/TODO.md and closes GitHub issues for completed TODO items.
  • Status Tracking: Ensures that the status of tasks in your documentation accurately reflects the state of your GitHub issues.
  • Use Case: When a new bug is reported on GitHub, it's automatically added to your team's central TODO list. When a developer marks a task as complete in the TODO list (and both main and kag branches are updated), the corresponding GitHub issue is automatically closed.

Quick Start

Use the sync-issues skill to synchronize GitHub issues with docs/TODO.md.

Frequently Asked Questions about sync-issues

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

FAQPage Schema
How do I sync GitHub issues with a local TODO.md file?

To sync GitHub issues with a local TODO.md file, this skill automates bi-directional synchronization by adding new open issues to your task list and closing GitHub issues for completed TODO items.

What are the requirements to close GitHub issues automatically from a TODO list?

Closing GitHub issues automatically from a TODO list requires adherence to specific completion criteria involving updates to both main and kag branches before the corresponding issue is closed.

Does the GitHub issues synchronization skill require the gh CLI tool?

Yes, this GitHub issues synchronization skill requires the gh CLI tool as a dependency to interact with your repository and manage the task tracking updates.

Can I use this to automatically add new GitHub issues to my task management documentation?

Yes, you can use this to automatically add new open GitHub issues to your local docs/TODO.md file, ensuring your project's task management documentation stays up-to-date across both platforms.

Why are my GitHub issues not closing when I mark TODO tasks as complete?

GitHub issues are not closing because the synchronization process requires both main and kag branches to be updated to meet the specific completion criteria before closing the corresponding GitHub issue.