task-sync

Task Sync

Local-first task tracking backed by a canonical tasks.json (with a generated, read-only TASKS.md view) that optionally reconciles with GitHub or Gitea issues. All logic lives in the bundled task_sync Python tool — this skill's job is invocation, table rendering, and human-in-the-loop decisions (conflict resolution, confidentiality review, the public-repo push warning). The tool never auto-resolves a conflict and never pushes anything without an explicit plan the user has seen.

Setup

The tool is bundled at tools/task-sync/src. Resolve the plugin root the same way other bundled-tool skills do, then invoke every subcommand through python3 -m task_sync:

PLUGIN_DIR="${CLAUDE_PLUGIN_ROOT:-$(find ~ -path '*/plugins/personal-plugin' -type d 2>/dev/null | head -1)}"
TOOL_SRC="$PLUGIN_DIR/tools/task-sync/src"

PYTHONPATH="$TOOL_SRC" python3 -m task_sync status

tasks.json lives at the target repo's root by default (--tasks tasks.json, resolved relative to the working directory). Pass --tasks <path> for any other location.

Version-skew preflight

Run this once, before the first subcommand, and report the result if it warns:

python3 - "$PLUGIN_DIR" <<'PY'
import json, os, re, sys
served = re.search(r"/personal-plugin/(\d+\.\d+\.\d+)(?:/|$)", sys.argv[1])
served = served.group(1) if served else None
reg = os.path.expanduser("~/.claude/plugins/installed_plugins.json")
try:
    entries = json.load(open(reg))["plugins"]["personal-plugin@troys-plugins"]
    installed = entries[0]["version"]
except Exception:
    installed = None
if served and installed and served != installed:
    print(f"WARNING: this session is serving personal-plugin {served}; "
          f"{installed} is installed. Run /reload-plugins to pick it up "
          f"(a full restart also works). "
          f"Until then this skill body may be older than the bundled tool.")
else:
    print(f"version-skew: none ({served or 'unknown'})")
PY

Why this exists. A running Claude Code session serves the plugin version it resolved at start-up. claude plugin update writes installed_plugins.json and prints "Restart to apply changes", but it does not change what the current session is already serving. So a long-lived session can run the current bundled tool from repo source while reading a stale skill body — a current tool against an old contract, with no error anywhere. That is #232: a session served an 11.3.0 body whose plan-JSON key list predated orphans, so the orphan findings the tool emitted were never read.