Skip to content
Skills Library
Management & product · Automation

sync-push

/sync-push

Push local taskboard ticket changes to GitHub Project board. Creates draft issues for new tickets and updates status for changed tickets. Use when you need to manually sync outbound changes.

Licence
Apache-2.0
Last repository change
17.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
1
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 17.10.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What to check before installing
  • SKILL.md zawiera komentarze HTML (1). Nie widać ich w podglądzie Markdown, a model je czyta.

What it does and when to use it

Push local taskboard ticket changes to GitHub Project board. Creates draft issues for new tickets and updates status for changed tickets. Use when you need to manually sync outbound changes.

Arguments

/sync-push Optional: --all to include done tickets
Original author description

Push local taskboard ticket changes to GitHub Project board. Creates draft issues for new tickets and updates status for changed tickets. Use when you need to manually sync outbound changes.

How it works

  1. Commands
  2. V2 Body Format
  3. When to Use
  4. Automatic Sync
  5. Prerequisites
Original SKILL.md headings · 44 lines, 227 words
SKILL.md preview
---
name: sync-push
description: "Push local taskboard ticket changes to GitHub Project board. Creates draft issues for new tickets and updates status for changed tickets. Use when you need to manually sync outbound changes."
argument-hint: "Optional: --all to include done tickets"
user-invokable: true
---

# /sync-push — Push Local Taskboard to GitHub Project

Push local taskboard ticket changes to the GitHub Project board (SpawnForge #2).

## Commands

```bash
# Incremental push (todo + in_progress + newly done)
cd project-forge && python3 .claude/hooks/github_project_sync.py push

# Full push (all tickets including done)
cd project-forge && python3 .claude/hooks/github_project_sync.py push-all

# Check sync status
cd project-forge && python3 .claude/hooks/github_project_sync.py status
```

## V2 Body Format

Push now syncs **full ticket content** to GitHub (not just status):
- **Body**: Description, priority, team, subtasks as `- [ ]`/`- [x]` checkboxes
- **Metadata block**: Hidden `<!-- SPAWNFORGE_METADATA -->` comment with ticketId, hashes, version
- **Change detection**: Only updates GitHub when bodyHash or subtaskHash changes
- **Format upgrade**: Old v1 tickets (`**Taskboard:** PF-N (ULID)`) auto-upgrade to v2 on next change
- **Rate limit guard**: If >10 tickets need format upgrade in incremental push, defers to `push-all`

## When to Use

- After bulk ticket operations (creating many tickets, reorganizing board)
- To verify sync state after network issues
- When `--all` is needed to backfill historical tickets to GitHub
- To bulk-upgrade all tickets to v2 body format (`push-all`)

## Automatic Sync

This runs automatically via the Stop hook after every response. Manual invocation is only needed for bulk operations or troubleshooting.

## Prerequisites

- `gh` CLI authenticated
- Taskboard API running on port 3010
- Python 3 available

Versions

RepositoryScoreLicence
This page · Tristan578/project-forge100Apache-2.0
jeremylongshore/tons-of-skills-marketplace100MIT

Database snapshot: 13.11.2026 · package version 66a49b25bccd (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100sync-pull
    Pull changes from GitHub Project board into local taskboard. Creates local tickets for new remote items and updates status for changed items. Use when you need to manually sync inbound changes from other contributors.
  • 90ticket-sync
    Push work items to the team's configured ticketing system (GitHub Issues, Jira, Azure DevOps, GitLab, Linear...). Use when asked to sync tickets, after closing out a plan, or when items should be visible in the tracker. Push and pull.
  • 100kanban
    Manage SpawnForge taskboard tickets — create, view, move, and sync to GitHub. Use when creating tickets, checking board state, syncing to GitHub before PRs, or managing the project backlog.
  • 100podio-ticket-updates
    Sync in-progress Podio Kanban tickets with progress from their linked GitHub repos — propose description updates and progress comments, apply after approval. Use when the user asks to update Podio tickets, sync ticket progress, or post status updates to the Kanban board.
  • 100gh-project-sync
    Reconciler between a GitHub Project (v2) board and a task-agent unified `tasks.yml`. Use when the user asks to "sync the project board with tasks.yml", "reconcile the GitHub project", "pull Todo cards into the task queue", "push completed tasks back to the board", or supplies…
  • 100github-sync
    Bidirectional sync between BMAD planning artifacts and GitHub Projects v2. Use this skill whenever the user says "sync to github", "push stories", "pull status from github", "set up github project", "github sync", "onboard github project", "create github issues from stories",…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.