菜单
Daily briefing — board, ecosystem activity, tracker sync, goals. Parallel 4-stream collection. Modes: --quick, --html. Trigger: "/briefing", "briefing", "good morning", "daily standup", "checkin", "morning briefing". (Bare "status" → bridge-status; bare "what is up" → dashboard.)
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
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".
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".
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".
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".
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".
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".
| name | briefing |
| description | Daily briefing — board, ecosystem activity, tracker sync, goals. Parallel 4-stream collection. Modes: --quick, --html. Trigger: "/briefing", "briefing", "good morning", "daily standup", "checkin", "morning briefing". (Bare "status" → bridge-status; bare "what is up" → dashboard.) |
| metadata | {"scope":"core"} |
Daily and on-demand briefing. Read the referenced file ONLY when triggered.
| Argument | Effect | Default |
|---|---|---|
(none) | Full briefing — all 4 streams + Phase 2 board.md sync | — |
--quick | Focus box + Stream A only; skips trackers, companion data, channels, Phase 2 | false |
--skip-trackers | All streams except Stream B (offline-friendly); Phase 2 still runs | false |
--commits YYYY-MM-DD | Detailed commit analysis for one day (sessions, time est., types) — see references/commit-analysis.md | — |
--html | After terminal output, delegate to /bridge-dashboard to render the operational HTML dashboard | false |
| Phase | default | --quick | --skip-trackers |
|---|---|---|---|
| Phase 0 (smart detection + day block) | ✅ | ✅ | ✅ |
| Stream A (local state) | ✅ | ✅ | ✅ |
| Stream B (trackers fan-out) | ✅ | ❌ | ❌ |
| Stream C (companion: calendar, imports) | ✅ | ❌ | ✅ |
| Stream D (channels) | ✅ | ❌ | ✅ |
| Phase 2 (board.md sync) | ✅ | ❌ | ✅ |
| Phase 3 (log entry) | ✅ | ✅ | ✅ |
| Phase 4 (terminal output) | ✅ | ✅ | ✅ |
bridge-config.yaml with work.enabled: true. If not: offer setup./briefing
is invoked standalone (e.g. via cron or a long-running session), manually
load protocols/standing-orders/*.md before Phase 1 — the applications
surface logic in Stream C depends on them.User wants to...
├── Full daily briefing → Read references/workflow.md
├── Quick local-only briefing → Read references/workflow.md (--quick path)
├── Detailed commit analysis → Read references/commit-analysis.md
├── Check for upstream CORE updates → Read references/upstream-summary.md
│ (only if `upstream:` block exists in
│ bridge-config.yaml AND a git remote
│ named `upstream` is configured;
│ Seed-repo instances skip)
└── Questions about briefing → Answer from this file
| For… | Use |
|---|---|
| Memory drift, doc-link health, branch/config sanity | /bridge-status |
| Live service status of channels/remotes (launchd, processes, ports) | /remote |
| Detailed GitHub/ADO board view (per-project) | /dashboard |
| Visual ops dashboard (Fleet + Board + Calendar + Channels) | /bridge-dashboard (also the target of --html) |
| Weekly archive | /archive |
/briefing is a daily rollup. The skills above are deeper dives into
a single dimension; cross-link rather than re-implement.
These describe what kind of work happened — used as the Type column
in work/log.md activity-log tables.
| Symbol | Name |
|---|---|
| 🧪 | Testing |
| 💻 | Development |
| 🔬 | Analysis |
| 📋 | Planning |
| 📝 | Documentation |
| 🔧 | DevOps |
| 📅 | Meeting |
| 📧 | Communication |
| 📁 | Documents |
| 🐛 | Bug / Incident |
| 🎓 | Talk / Teaching |
| 🧠 | Insight / Sequential-thinking |
Distinct from the commit-message classification taxonomy in
references/commit-analysis.md — that one is for analyzing git history
(🐛 Bug Fixing, 🎯 Feature, 🔧 Code Refactoring, …). The taxonomies overlap
on a few icons but address different artefacts; don't try to unify them.