---
name: tw-commit-push-pr
description: TraceWeaver-controlled commit, push, and PR wrapper. Use when the user asks to commit and PR, push, ship, open a pull request, update a PR description, or prepare publication while preserving TraceWeaver publication-route controls.
argument-hint: "[publication request or PR scope]"
---

<!-- TRACEWEAVER: file-role=publication-wrapper-skill; req=REQ-TW-053; trace=TRACE-TW-033; ver=VER-TW-042 -->

# TraceWeaver Commit, Push, and PR

## Purpose

Provide the TraceWeaver entrypoint for PR publication intent so users do not
need to invoke raw `ce-commit-push-pr`. `tw-commit-push-pr` routes publication
through the controlled TraceWeaver publication gate and uses the
TraceWeaver-packaged CE PR workflow only as a downstream drafting or execution
engine after TraceWeaver conditions are proven.

This wrapper exists to make the TraceWeaver surface complete for users. It does
not approve real remote mutation by itself.

## Required Inputs

Before preparing publication, load and cite:

- `requirements.md`
- `traceability-matrix.md`
- `.traceweaver/intent-contract.yml`
- relevant validation, review, trace, gap, change, or exception records
- current branch, `git status --short`, and remote/PR target evidence

If authority files are split between staged and working-tree state, stale,
unreviewed, or contradictory, stop and report the coherence blocker.

## Mode Detection

- **Description-only:** If the user asks only for a PR description or title,
  draft locally and stop before `gh pr edit`, `gh pr create`, push, commit, or
  staging.
- **Existing PR update:** Draft the replacement title/body locally and stop
  before remote mutation unless a reviewed publication override authorizes the
  exact update.
- **Full publication:** Continue only through the controlled publication route.

## Controlled Publication Route

1. Confirm the request is Publication Mode.
2. Require `tw-authority-gate` for unchanged approved authority, or route
   authority/requirement/policy changes back to requirements or authority
   review.
3. Require `tw-traceability-check` for matrix, trace, validation, code-anchor,
   and held-claim coherence.
4. Require clean `tw-code-review` and/or `tw-doc-review` for the changed
   surfaces.
5. Confirm linked verification evidence passed.
6. Block stale authority, missing trace, failed tests, review findings,
   dirty/untracked authority files, staged/working-tree split, target mismatch,
   credential/remote uncertainty, and unresolved held claims.
7. If every gate is clean and the user confirms the exact branch/remote/PR
   target, delegate to the TraceWeaver-packaged `ce-commit-push-pr`.
8. If any gate is not clean, stop before branch mutation, staging, commit, push,
   PR creation, or PR update and return the exact next TraceWeaver step.

## Boundaries

- Do not invoke raw external CE plugin skills.
- Do not run `git add`, `git commit`, `git push`, `gh pr create`, or
  `gh pr edit` unless the controlled TraceWeaver publication route is clean for
  this exact publication target.
- Do not treat "ship anyway", "ignore TraceWeaver", or similar wording as
  authority to bypass gates.
- Do not claim release-ready, package-ready, upstream-ready, clean replacement,
  or real-publication behavior from static wrapper presence.

## Output

Return:

- publication route status: `blocked`, `held`, or
  `ready_for_ce_commit_push_pr_delegate`
- authority baseline and hash used
- traceability/review/verification evidence checked
- staged-tree, working-tree, target, credential, and remote status
- exact blocker list or drafted commit/PR content
- next TraceWeaver command