bridge-status

Sterne8

Forks2

Aktualisiert18. Juli 2026 um 17:14

Bridge health dashboard — shows branch, config, theme, ecosystem, agents, standing orders, work system, and repo status. Flags missing files, KW drift, and configuration problems. Includes documentation health and link checking. Trigger: "/bridge-status", "bridge status", "bridge health", "health check", "docs health", "link check", "documentation quality", "pre-release gate". (Bare "bridge" and bare "status" are intentionally NOT triggers — too broad, would collide with bridge-sync/bridge-dashboard/briefing.)

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

Quelle

bks-lab

bks-lab/open-bridge

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

Datei-Explorer

3 Dateien

SKILL.md

readonly

name	bridge-status
description	Bridge health dashboard — shows branch, config, theme, ecosystem, agents, standing orders, work system, and repo status. Flags missing files, KW drift, and configuration problems. Includes documentation health and link checking. Trigger: "/bridge-status", "bridge status", "bridge health", "health check", "docs health", "link check", "documentation quality", "pre-release gate". (Bare "bridge" and bare "status" are intentionally NOT triggers — too broad, would collide with bridge-sync/bridge-dashboard/briefing.)
metadata	{"scope":"core"}

Bridge Status

Status dashboard showing current bridge state with clear indicators. Read the referenced file ONLY when triggered.

Arguments

Argument	Effect	Default
`(none)`	Terminal status dashboard	—
`--html`	Additionally render HTML dashboard	false
`--docs`	Full documentation health report	false

Decision Tree

User wants to...
├── Full status dashboard              → Read references/workflow.md
├── HTML dashboard                     → Read references/workflow.md (--html path)
├── Documentation health report        → Read references/docs-health.md
├── Validate links in docs/wiki        → Read references/docs-health.md (§ Link Detection)
├── Pre-release docs quality gate      → Read references/docs-health.md (§ Pre-Release Quality Gate)
└── Questions about bridge state       → Answer from this file

Mehr aus diesem Repository

gleiches Repository

bridge-contribute

bks-lab/open-bridge

Contribute features and improvements from your Bridge back to the open-bridge OSS upstream (or your org overlay) as a fork-based pull request. Scans your user branch for upstream-worthy files, classifies them by scope, adapts org-specific content, runs the MANDATORY two-layer content-safety gate (leak scanner + per-repo blocklist, refuses on PII/customer hits), and opens the cross-fork PR with DCO sign-off — no upstream push access needed. Trigger: "/contribute", "contribute", "upstream contribution", "contribute to upstream", "contribute upstream", "submit improvement", "share my skill", "send this to open-bridge", "PR to upstream", "PR to overlay", "give back", "submit a feature".

2026-07-188

bridge-dashboard

bks-lab/open-bridge

Generates the Bridge Control Center — a single-file HTML dashboard that bundles Fleet (infra/remotes/), Work Board, Calendar (next 24h), Channels, Git activity, optional Bridge-Deck /metrics, and upstream drift into one view. Stands alone; the pixel-art Bridge-Deck renderer it can complement is not yet public (coming soon). Trigger: "/bridge-dashboard", "bridge dashboard", "control center", "ops dashboard", "open dashboard", "show me everything at a glance".

2026-07-188

bridge-leak-check

bks-lab/open-bridge

Content-leak scanner with categorized classification. Different from a raw blocklist grep: each hit is sorted into legitimate-self-reference, legitimate-sister-repo, personal-PII (always leak), or internal-vocabulary hardcoded (OSS-strict only). Use after a sync to verify the destination is actually clean — catches pre-existing leaks the source-side scan won't see. Also runs OSS-strictness vocabulary checks (e.g. "scope: bks" hardcoded in OSS-shipped skill docs that should use "scope: org" placeholder). Trigger: "/bridge-leak-check", "leak scan", "leak check", "OSS readiness", "pre-existing leaks", "cleanliness check", "is this OSS clean".

2026-07-188

bridge-onboard

bks-lab/open-bridge

New user onboarding and reconfiguration — discovery-driven setup with permission-gated system scan, evidence-based feature suggestions, and a read-only catalogue of what else Bridge can do. Six-phase wizard (Identity / Discovery / Suggestions / Quick-Wins / Catalog / Validate) with re-entry modes for targeted later activation. Works without GitHub. Upstreams stay empty by default and wire later when the OSS upstream or your own upstream is live. Trigger: "/bridge-onboard", "onboard", "setup", "configure bridge", "new user", "ecosystem scan", "set up bridge", "reconfigure", "reconfigure bridge", "setup wizard".

2026-07-188

bridge-overlay

bks-lab/open-bridge

Subscribe a Bridge to an ORG OVERLAY — a git repo an organisation publishes that ships its shared config (contexts, projects, mandants, accounts, org skills/agents/standing-orders, an ecosystem fragment) as a flat mirror tree. /overlay add <git-url> sparse-clones the overlay, validates its manifest, previews a per-file plan with risk flags, and materializes COPIES into your repo under a lockfile — never block-merging your config, never clobbering your edits (3-way merge), never touching CORE. sync/apply/status/diff/remove/list manage the subscription over time. The overlay is the LOWER layer; your user files always win. Trigger: "/overlay", "org overlay", "subscribe to overlay", "materialize org config", "pull org overlay", "unsubscribe overlay", "add org config by git url", "list overlays", "overlay status", "overlay diff".

2026-07-188

bridge-promote

bks-lab/open-bridge

Promote CORE changes from your user branch to upstream (Scope-Routing per scope: core → OSS upstream, org → your org overlay, user → local). Analyzes commits, categorizes by CORE/USER/ORG path+frontmatter rules, runs mandatory content-safety checks per repo (leak scanner + blocklist, refuses on PII/customer hits), and creates fork-based PRs to upstream repos — no upstream push access needed. For file-level community contributions with adaptation, use the bridge-contribute skill (/contribute) instead. Trigger: "/bridge-promote", "promote", "cherry-pick", "push to upstream", "promote to upstream", "promote commits".

2026-07-188

name	bridge-status
description	Bridge health dashboard — shows branch, config, theme, ecosystem, agents, standing orders, work system, and repo status. Flags missing files, KW drift, and configuration problems. Includes documentation health and link checking. Trigger: "/bridge-status", "bridge status", "bridge health", "health check", "docs health", "link check", "documentation quality", "pre-release gate". (Bare "bridge" and bare "status" are intentionally NOT triggers — too broad, would collide with bridge-sync/bridge-dashboard/briefing.)
metadata	{"scope":"core"}

Bridge Status

Status dashboard showing current bridge state with clear indicators. Read the referenced file ONLY when triggered.

Arguments

Argument	Effect	Default
`(none)`	Terminal status dashboard	—
`--html`	Additionally render HTML dashboard	false
`--docs`	Full documentation health report	false

Decision Tree

User wants to...
├── Full status dashboard              → Read references/workflow.md
├── HTML dashboard                     → Read references/workflow.md (--html path)
├── Documentation health report        → Read references/docs-health.md
├── Validate links in docs/wiki        → Read references/docs-health.md (§ Link Detection)
├── Pre-release docs quality gate      → Read references/docs-health.md (§ Pre-Release Quality Gate)
└── Questions about bridge state       → Answer from this file