sync

Synchronizes GitHub issue/PR states with CLAUDE.md TODO items.

Updated Jan 24, 2026
One-click install
npx skills add https://github.com/ereferen/zellij-toolbox --skill sync-ereferen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync
Source: https://github.com/ereferen/zellij-toolbox/tree/main/.claude/skills/sync
Command: npx skills add https://github.com/ereferen/zellij-toolbox --skill sync-ereferen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This workflow keeps GitHub issues and CLAUDE.md TODO items in sync by identifying issues that should be closed by merged PRs and by updating the TODOs based on implemented tasks.

Core Features & Use Cases

  • Issue/PR state reconciliation: Detects which issues should be closed by merged PRs and updates status accordingly.
  • CLAUDE.md TODO alignment: Cross-checks CLAUDE.md TODO items with issue content to reflect progress.
  • Progress reporting: Produces a tabular summary of issues, PRs, and TODO statuses for quick review.
  • Extensible integration: Works with existing GitHub workflows and CLAUDE.md documents to streamline project management.

Quick Start

Run the synchronization workflow to align open and closed issues with the CLAUDE.md TODO list.

Frequently Asked Questions about sync

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

FAQPage Schema
How do I sync GitHub issues with CLAUDE.md TODO items?

You can sync GitHub issues with CLAUDE.md TODO items by running an automated synchronization workflow that detects issues closed by merged pull requests and updates the TODO list to reflect implemented work. It cross-checks issue content with CLAUDE.md scaffolding to align project status.

Can I automatically close GitHub issues when a pull request is merged?

Yes, you can automatically close GitHub issues when a pull request is merged through issue and PR state reconciliation. The synchronization workflow detects which open issues should be closed by merged PRs and updates their status accordingly to maintain accurate project tracking.

What is the best way to keep CLAUDE.md TODOs aligned with GitHub pull request states?

The best way to keep CLAUDE.md TODOs aligned with GitHub pull request states is to use a synchronization workflow that cross-checks CLAUDE.md TODO items against issue and PR content, producing a tabular summary of statuses to ensure TODOs accurately reflect implemented work.

Do I need external dependencies to synchronize GitHub issues and CLAUDE.md files?

No, you do not need external dependencies to synchronize GitHub issues and CLAUDE.md files beyond GitHub APIs and local CLAUDE.md scaffolding. The workflow operates natively within your existing GitHub repositories and CLAUDE.md documentation without requiring additional packages.

Why are my GitHub issues not closing after a pull request is merged?

GitHub issues may not close after a pull request is merged if there is no synchronization mechanism detecting the state reconciliation. Running an automated sync workflow identifies merged PRs and closes the appropriate issues, ensuring your CLAUDE.md TODOs and GitHub repository states match.

How does CLAUDE.md TODO synchronization work with existing GitHub workflows?

CLAUDE.md TODO synchronization works with existing GitHub workflows by using extensible integration that reads GitHub issue and PR states via GitHub APIs. It cross-checks this data with your local CLAUDE.md document, updating TODO items and generating a progress report for quick review.