sync-issues

Synchronize GitHub issues with docs/todo.md using GitHub CLI.

108|19|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/minorun365/marp-agent --skill sync-issues-minorun365
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync-issues
Source: https://github.com/minorun365/marp-agent/tree/main/.agents/skills/sync-issues
Command: npx skills add https://github.com/minorun365/marp-agent --skill sync-issues-minorun365

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates synchronization between GitHub issues and the repository's docs/todo.md so task assignment and issue state remain consistent without manual bookkeeping.

Core Features & Use Cases

  • Two-way synchronization: Add new open GitHub issues to docs/todo.md and close GitHub issues when corresponding TODO rows are marked complete.
  • Conditional closure rules: Enforce closure only when both main and kag implementation columns are complete (✅ or ➖), preventing premature issue closing.
  • Transparent operations: Use GitHub CLI to list, view, and close issues and show diffs of docs/todo.md updates for review before committing changes.

Quick Start

Run the sync to add open GitHub issues to docs/todo.md and close corresponding issues only when both main and kag implementation columns are marked complete.

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 todo.md file automatically?

To sync GitHub issues with a todo.md file, this Skill uses GitHub CLI to list open issues and add them as new TODO entries in docs/todo.md, keeping task lists and issue states aligned without manual updates.

When does the Skill close GitHub issues during task list synchronization?

The Skill closes GitHub issues during synchronization only when both the main and kag implementation columns in docs/todo.md are marked complete with a checkmark or dash, preventing premature closure of incomplete tasks.

Do I need GitHub CLI to synchronize issues with docs/todo.md?

Yes, you need GitHub CLI installed and authenticated, because the Skill depends on it to list, view, and close GitHub issues while parsing and updating the docs/todo.md task table.

What is the best way to keep GitHub issues and TODO task tables aligned?

The best way to keep GitHub issues and TODO task tables aligned is using two-way synchronization that adds new open issues to docs/todo.md and conditionally closes issues when implementation columns are complete.

Can I review docs/todo.md changes before GitHub issues are closed?

Yes, you can review changes before GitHub issues are closed, because the Skill shows diffs of docs/todo.md updates for review before committing any synchronization changes to your repository.