issue-sync

Issue Sync

Push local updates as GitHub issue comments for transparent audit trail.

Usage

/pm:issue-sync <issue_number>

Required Rules

IMPORTANT: Before executing this command, read and follow:

• .claude/rules/datetime.md - For getting real current date/time

Preflight Checklist

Before proceeding, complete these validation steps. Do not bother the user with preflight checks progress ("I'm not going to ..."). Just do them and move on.

1. GitHub Authentication:

   • Run: gh auth status
   • If not authenticated, tell user: "❌ GitHub CLI not authenticated. Run: gh auth login"

2. Issue Validation:

   • Run: gh issue view $ARGUMENTS --json state
   • If issue doesn't exist, tell user: "❌ Issue #$ARGUMENTS not found"
   • If issue is closed and completion < 100%, warn: "⚠️ Issue is closed but work incomplete"

3. Local Updates Check:

   • Check if .claude/epics/*/updates/$ARGUMENTS/ directory exists
   • If not found, tell user: "❌ No local updates found for issue #$ARGUMENTS. Run: /pm:issue-start $ARGUMENTS"
   • Check if progress.md exists
   • If not, tell user: "❌ No progress tracking found. Initialize with: /pm:issue-start $ARGUMENTS"

4. Check Last Sync:

   • Read last_sync from progress.md frontmatter
   • If synced recently (< 5 minutes), ask: "⚠️ Recently synced. Force sync anyway? (yes/no)"
   • Calculate what's new since last sync

5. Verify Changes:

   • Check if there are actual updates to sync
   • If no changes, tell user: "ℹ️ No new updates to sync since {last_sync}"
   • Exit gracefully if nothing to sync

Instructions

You are synchronizing local development progress to GitHub as issue comments for: Issue #$ARGUMENTS

1. Gather Local Updates

Collect all local updates for the issue:

• Read from .claude/epics/{epic_name}/updates/$ARGUMENTS/
• Check for new content in:
  • progress.md - Development progress
  • notes.md - Technical notes and decisions
  • commits.md - Recent commits and changes
  • Any other update files