bridge-dev

Plugin bridge-dev from marketplace bridge in darkstar1227/bridge. Commands read from the repo's manifest — 1 month ago.

Skills (17)

• agy-second-voice

  Get an independent, read-only second opinion from Antigravity CLI (`agy`, Google's coding agent) — review the current diff, adversarially challenge it, or consult it on a question/plan — as a cross-model check alongside Claude's own analysis. Use when asked to "agy review", "agy challenge", "ask agy

• autoresearch-impl

  Runs a Karpathy-autoresearch-style keep-or-discard iteration loop over an already-implemented branch — propose one variant, run it against tests/benchmarks, keep it if the metric improves or discard and revert, repeat within a fixed budget — before handing off to code-review/QA. Use this after subag

• autoresearch-plan

  Runs a Karpathy-autoresearch-style comparative experiment loop over candidate technical approaches (API designs, algorithms, data-flow strategies) after a plan has been reviewed but before it's handed to an implementer. Picks a winning approach against an explicit metric and records the baseline, so

• benchmark-opencode-models

  Deep-benchmark which OpenCode models are actually viable for opencode-bridge — ping each candidate model, then run 5 canned superpowers-style task prompts per model (feature vs bugfix, short vs detailed, plus a dedicated TDD red-to-green prompt), independently verify every result by executing the ge

• check-opencode-models

  Fast two-stage check for a list of OpenCode models — ping (reachability/auth) followed by one real, minimal single-shot prompt test to catch models that ping fine but are actually slow or wrong under real dispatch. Reports which models are usable right now vs. reachable-but-slow vs. reachable-but-wr

• full-pipeline

  Orchestrates the user's full end-to-end workflow in order — gstack office-hours, autoplan, autoresearch-plan, superpowers writing-plans and subagent-driven-development, autoresearch-impl, code-review, and qa — invoking each skill in sequence and handing its output forward as the next step's input. A

• gstack-to-plan

  Bridge a gstack-reviewed plan into a Superpowers writing-plans implementation plan. Reads the latest approved gstack plan, transforms it into a Superpowers-compatible spec, then invokes superpowers:writing-plans.

• init-project

  Detect a target project's stack (Python/uv, Node/TypeScript, Docker, Supabase, Git) and initialize or audit it against standard conventions — ruff/PEP8 or eslint/prettier, docker-compose profiles, Supabase migrations, .env hygiene, commit/branch conventions, folder layout — then write the result int

• opencode-bridge

  Delegate a coding task to OpenCode and get back a structured handoff report (done/failed/timed-out, files changed, implementation summary) — for use as an OpenCode-backed implementer step in subagent-driven-development or executing-plans. For a full plan-execution loop with review gates already wire

• opencode-subagent-driven-development

  Wraps Superpowers' subagent-driven-development plan-execution loop, asking upfront whether the implementer step should be a Claude subagent (default) or OpenCode via opencode-bridge — spec-compliance and code-quality review stay identical either way.

• review-pipeline-logs

  Query a project's local log files and review whether a just-developed application pipeline actually ran the way it was designed to. Reads the project's design/plan doc for the expected steps, parses the relevant log file(s), then checks the run against the plan step-by-step, flags errors/exceptions,

• send-update-email

  Send a readable, version-grouped update email for a single repo's accumulated commits since the last send, via Resend or a fully custom HTTP POST depending on the repo's configured provider — shows the rendered content and waits for confirmation before actually sending.

• setup-email-updates

  Create or edit the .bridge/email-config.json that send-update-email needs — recipients, last-sent tracking, and either a per-repo Resend MCP connection or a fully custom HTTP POST structure (endpoint, headers, body template), chosen per repo — for a single repo or in bulk across a parent folder. Alw

• setup-env

  Export the user-scope Claude Code plugins, marketplaces, and gstack installation on this machine into a portable manifest, or install from an existing manifest onto a new machine to reproduce the same Claude Code environment. Trigger when the user wants to back up their plugin setup, replicate their

• setup-relay-provider-template

  Wire cancerfreebiotech/claude-profile-kit's claude-project-template (orchestrator + 7 specialized subagents + native advisor) into the current project, driven entirely by an already-configured relay LiteLLM provider — queries the provider's gateway for its real model list, assigns a model per role,

• sre-assessment

  Runs an on-demand Site Reliability Engineering assessment of a project — SLO/SLI coverage, error budgets, observability (metrics/logs/traces/alerting), incident readiness (runbooks, on-call, postmortems), deploy safety (rollback, canary, feature flags), capacity/scaling, and dependency/failure-mode

• superpowers-pipeline

  A lighter orchestrator than full-pipeline — chains only the core Superpowers loop (writing-plans, subagent-driven-development, finishing-a-development-branch) without gstack's office-hours/autoplan or the autoresearch experiment steps, for when a spec already exists or gstack-level planning isn't wa

Similar plugins