sync

Solid

Dispatcher 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.

AI & Automation 38 stars 3 forks Updated today Apache-2.0

Install

View on GitHub

Quality Score: 83/100

Stars 20%
53
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# /sync — bidirectional origin↔upstream sync dispatcher `/sync <subcommand>` routes origin↔upstream sync operations. The first whitespace-delimited token of `$ARGUMENTS` selects the subcommand; the remainder is that subcommand's own argument string. Each subcommand's full procedure lives in a reference doc under `references/` — read that doc and follow it as the authoritative instructions. The canonical topology (origin=operator fork, upstream=mifunedev canonical) and the intentional divergences that every sync must preserve live in `references/topology.md`. Read it before executing any subcommand. ## Subcommands | Subcommand | Direction | Purpose | Procedure | |---|---|---|---| | `publish` | origin→upstream | Branch off upstream/development, merge-no-commit origin/development, sanitize private state, reconcile structure, eval-gate, draft PR to upstream | `references/publish.md` | | `catchup` | upstream→origin | Cherry-pick the squash commit of a specific upstream feature onto origin/development; never `git merge upstream/development` | `references/catchup.md` | | `status` | read-only | Invoke `/audit drift` and interpret its section (A) framework-drift output to report which direction is needed | inline — see below | ## Dispatch ```bash ARGUMENTS="${ARGUMENTS:-}" SUB="${ARGUMENTS%% *}" # first token REST="${ARGUMENTS#"$SUB"}" # everything after it REST="${REST# }" # trim one leading space ``` Route on `$SUB`: | `$SUB` | Action | |--------...

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

AI & Automation Listed

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".

8 Updated today
bks-lab
AI & Automation Listed

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".

8 Updated today
bks-lab
Code & Development Listed

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.

10 Updated 3 weeks ago
rezathepure