sync
SolidDispatcher for bidirectional origin↔upstream harness sync — routes the first token of $ARGUMENTS to one of three subcommands: publish (origin→upstream), catchup (upstream→origin), or status (read-only direction check). The canonical topology and intentional divergences to preserve live in references/topology.md. Full per-subcommand procedures live in references/{publish,catchup}.md. This dispatcher composes /audit drift (framework drift detection), /eval (oracle floor), /audit pr (promotability), and /git (branch/PR/CHANGELOG conventions). It NEVER reimplements drift detection — /audit drift owns that. TRIGGER when: "sync to upstream", "publish fork changes to the public repo", "push to mifunedev", "origin→upstream" → publish; "pull from upstream", "port a feature from upstream", "catchup from mifunedev", "upstream→origin" → catchup; "check sync status", "how far behind are we", "which direction needs sync" → status.
Install
Quality Score: 83/100
Skill Content
Details
- Author
- mifunedev
- Repository
- mifunedev/openharness
- Created
- 5 months ago
- Last Updated
- today
- Language
- TypeScript
- License
- Apache-2.0
Similar Skills
Semantically similar based on skill content — not just same category
bridge-sync
End-of-sprint batch-sync: pushes ALL pending scope:core + scope:org commits from the local user branch to BOTH upstreams (open-bridge + your org overlay) in one operation, with per-destination scrubbing and parallel PR creation. Complements /promote (per-commit) and /contribute (per-file) with a sprint-level workflow. Trigger: "/bridge-sync", "sync to upstreams", "push to both", "batch promote", "end-of-sprint sync", "sync all pending", "push everything to both repos".
tracker-sync
Persistent snapshot + bidirectional reconcile between The Bridge tasks and GitHub Project boards. Pulls each board into work/trackers/<provider>/<slug>.json (the local mirror / dump), diffs it against work/tasks|streams/*/STATUS.md sync.github bindings into a delta table (in_sync · remote_ahead · local_ahead · state_mismatch · orphan_local · orphan_remote), and pushes local→remote changes through github-projects-manager — gated, never auto. GitHub is the system of record, The Bridge is the cockpit (remote-authoritative). Trigger: "/tracker-sync", "tracker sync", "sync my tasks", "reconcile tasks", "board reconcile", "snapshot github", "which task is in which state", "github project dump", "sync tasks down", "sync tasks up", "task drift", "sync status".
sync-upstream
Bring this fork up to date with claude-code-best/claude-code. Use whenever the user asks to sync with upstream, pull in upstream changes, check whether the fork is behind, update from claude-code-best, or merge the latest from the original repo.