Menú
Create an implementation proposal through the governed bridge-propose helper for Loyal Opposition review.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Sweep and locally commit all current non-ignored GroundTruth-KB worktree changes after owner authorization. Use when the owner says to "sweep commit", "commit everything", "commit all changes", consolidate verified bridge work, or perform the regular GT-KB full-worktree cleanup commit. Handles GT-KB governance hooks, inventory drift, narrative-artifact approval evidence, staged credential scans, and verification before committing. Does not push unless the owner explicitly asks.
Sweep and locally commit all current non-ignored GroundTruth-KB worktree changes after owner authorization. Use when the owner says to "sweep commit", "commit everything", "commit all changes", consolidate verified bridge work, or perform the regular GT-KB full-worktree cleanup commit. Handles GT-KB governance hooks, inventory drift, narrative-artifact approval evidence, staged credential scans, and verification before committing. Does not push unless the owner explicitly asks.
Sweep and locally commit all current non-ignored GroundTruth-KB worktree changes after owner authorization. Use when the owner says to "sweep commit", "commit everything", "commit all changes", consolidate verified bridge work, or perform the regular GT-KB full-worktree cleanup commit. Handles GT-KB governance hooks, inventory drift, narrative-artifact approval evidence, staged credential scans, and verification before committing. Does not push unless the owner explicitly asks.
Sweep and locally commit all current non-ignored GroundTruth-KB worktree changes after owner authorization. Use when the owner says to "sweep commit", "commit everything", "commit all changes", consolidate verified bridge work, or perform the regular GT-KB full-worktree cleanup commit. Handles GT-KB governance hooks, inventory drift, narrative-artifact approval evidence, staged credential scans, and verification before committing. Does not push unless the owner explicitly asks.
Orchestrate the deterministic `gt hygiene sweep` CLI and route deterministic inventory-backed string scans to `gt admin inventory refresh` plus `gt admin inventory scan-strings` instead of ad hoc grep loops. Use when investigating config-drift class observations, inventory-wide string checks, repeated config defects, or session-start hygiene thresholds; classify findings by artifact lifecycle trigger category per DCL-ARTIFACT-LIFECYCLE-TRIGGERS-001 and guide owner-gated remediation child-bridge filing.
Orchestrate the deterministic `gt hygiene sweep` CLI and route deterministic inventory-backed string scans to `gt admin inventory refresh` plus `gt admin inventory scan-strings` instead of ad hoc grep loops. Use when investigating config-drift class observations, inventory-wide string checks, repeated config defects, or session-start hygiene thresholds; classify findings by artifact lifecycle trigger category per DCL-ARTIFACT-LIFECYCLE-TRIGGERS-001 and guide owner-gated remediation child-bridge filing.
| name | send-review |
| description | Create an implementation proposal through the governed bridge-propose helper for Loyal Opposition review. |
| argument-hint | <descriptive-name> |
| allowed-tools | Read, Write, Edit, Bash, Glob |
| license | Proprietary - Remaker Digital |
| compatibility | ["claude-code >= 1.0"] |
| metadata | {"project":"agent-red-customer-experience","category":"bridge-coordination","governance":"file-bridge-protocol"} |
Compatibility alias for filing a Prime Builder proposal through the governed
gtkb-bridge-propose helper path. Do not write proposal files directly, and do
not create or restore aggregate queue artifacts.
Arguments: $ARGUMENTS = descriptive kebab-case name for the proposal (e.g., widget-refactor).
Determine the descriptive name from $ARGUMENTS. If not provided, derive
a kebab-case topic_slug from the current work context.
Draft the proposal content with the required bridge sections from
.claude/rules/file-bridge-protocol.md, including specification links,
project/work-item metadata when implementation-targeting, prior
deliberations, owner input when applicable, and a spec-derived verification
plan.
File through gtkb-bridge-propose. Use the helper-mediated bridge writer
described in .claude/skills/bridge-propose/SKILL.md. The helper performs
credential scanning, bridge-compliance validation for Codex paths, proposal
file creation, author metadata insertion, and dispatcher/TAFE bridge-state
publication via gtkb-bridge-propose.
Report the helper result: created proposal path, bridge document slug, status line, and any helper error that blocked filing.
/send-review widget-refactor
The helper creates bridge/widget-refactor-001.md and reports a registration
like:
Document: widget-refactor
NEW: bridge/widget-refactor-001.md
The example output above is produced by the bridge-propose helper. This skill is only the caller-facing alias.