sync-pull

Pull GitHub Project board changes into the local taskboard.

5|1|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/Tristan578/project-forge --skill sync-pull
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync-pull
Source: https://github.com/Tristan578/project-forge/tree/main/.agents/skills/sync-pull
Command: npx skills add https://github.com/Tristan578/project-forge --skill sync-pull

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pull changes from the GitHub Project board into the local taskboard, creating local tickets for new remote items and updating status for changed items. This keeps remote and local work items aligned, reducing manual syncing and inconsistencies.

Core Features & Use Cases

  • Two-way synchronization: pulls changes from GitHub and updates local tickets to reflect remote status and content.
  • Subtask and body syncing: imports subtasks and description/body changes to keep local tickets in sync with remote items.
  • Automatic linking and re-linking: preserves mappings and re-links tickets if IDs drift or mappings are lost, avoiding duplicates.
  • Backward compatibility: continues to parse older v1 ticket formats while supporting new v2 structures.
  • Automatic session sync: runs at session start to keep local state up-to-date with minimal user input.

Quick Start

Start a session by running the sync-pull workflow to bring remote GitHub changes into the local taskboard.

Frequently Asked Questions about sync-pull

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

FAQPage Schema
How do I sync GitHub project board changes to a local taskboard?

To sync a GitHub project board to a local taskboard, run the sync-pull workflow at session start to pull remote updates, create local tickets for new items, and update existing ones to mirror the GitHub board.

What is two-way synchronization between GitHub Projects and a local taskboard?

Two-way synchronization between GitHub Projects and a local taskboard pulls remote changes to update local ticket status and content, including subtasks and body syncing, preserving mappings to keep both states aligned.

Does sync-pull support importing GitHub subtasks and ticket body changes?

Yes, sync-pull supports importing GitHub subtasks and description body changes. It syncs these elements to keep local tickets fully updated with remote item content during the synchronization process.

How does GitHub ticket synchronization handle lost mappings or drifting IDs?

GitHub ticket synchronization handles lost mappings or drifting IDs through automatic linking and re-linking. This preserves existing mappings and avoids creating duplicate local tickets when remote IDs change.

Can I import older v1 format tickets from a GitHub Project board?

Yes, you can import older v1 format tickets from a GitHub Project board. The synchronization process offers backward compatibility, continuing to parse v1 ticket formats while supporting new v2 structures.

When should I run a GitHub project board sync to update my local tickets?

You should run a GitHub project board sync at session starts or after remote updates occur. This ensures your local state accurately mirrors the GitHub board with minimal manual input.