vibe-export-kanban

vibe-export-kanban

Overview

One-way sync from a completed local run back to vibe-kanban. For each issue in plan-local.json that has a kanban_id, post a "merged" comment with the final PR url and the commit SHA, then transition the issue to done. Idempotent — re-running is safe.

Core principle: Comment + transition only. Never touch title, description, tags, or relationships. Teammates own the canonical metadata; we just close the loop.

Announce at start: "I'm using the vibe-export-kanban skill to sync results back."

When to use

• vibe-ship-fast finished, the final PR is merged to main (verified via gh pr view --json state)
• .vibe-flow/plan-local.json exists and at least one issue has a non-null kanban_id

Do NOT use if:

• Final PR is still open or closed-without-merge → wait or abandon
• Plan was created by vibe-plan --local (no kanban links) → nothing to export, exit early with a message
• A previous export already ran for this commit (detected via marker comment) → no-op confirmation

The process

Step 1: Verify preconditions

# Final PR must be merged
PR_URL=$(jq -r '.pr_url' .vibe-flow/state-local.json)
PR_NUM=$(echo "$PR_URL" | grep -oE '[0-9]+$')
STATE=$(gh pr view "$PR_NUM" --json state,mergeCommit --jq '.state')
[ "$STATE" = "MERGED" ] || { echo "PR $PR_NUM not merged (state=$STATE)"; exit 1; }
MERGE_SHA=$(gh pr view "$PR_NUM" --json mergeCommit --jq '.mergeCommit.oid')

If preconditions fail → STOP, report to user.

Step 2: Load plan + state

Read .vibe-flow/plan-local.json and .vibe-flow/state-local.json. Build the export set:

for each issue in plan-local.json.issues:
  if issue.kanban_id is null → skip (local-only)
  if state-local.json.issues[issue.id].status != "merged" → skip (not actually shipped this run)
  else → include in export set

If export set is empty → output "nothing to sync" and exit.

Step 3: Check the idempotency marker

For each issue in the export set, call list_issue_comments(issue_id) (or equivalent MCP read). Look for an existing comment containing: