Menu
Push the current branch to `origin` and create or update the matching GitHub PR for this repository.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Use when any Mister Smith request touches Linear, GitHub PR flow, packet slicing, review state, workspace hygiene, or bootstrap readiness and needs the correct Smith MCP route first.
Use after a Mister Smith SpecKit packet has been created and needs post-spec closure: packet verification, git closure, Linear materialization, honest execution-lane preparation, and follow-on execution readiness without implementation unless explicitly requested.
Use when the user wants a complete Mister Smith live runtime session or workflow evaluation with real execution, durable evidence capture, and honest task/session/autonomy proof instead of mock-only validation.
Use when Mister Smith needs spec-only frontier packet work: turning current repo truth or a pre-SpecKit primer into a new product-side SpecKit packet, or running the full local SpecKit authoring chain for an already chosen packet. Trigger for requests to create or extend a Mister Smith packet spec, pre-SpecKit primer, specify-init prompt, or full spec bundle without implementation.
Use when a Mister Smith SpecKit phase or tasks pack needs to be turned into deterministic Linear slices, blocker chains, prep-slice opportunities, and direct-execution-ready work.
Legacy-named skill for Mister Smith tasks that span Linear control-plane state, GitHub PR flow, local repo truth, lifecycle recovery, or workspace hygiene.
| name | push |
| description | Push the current branch to `origin` and create or update the matching GitHub PR for this repository. |
gh is installed and authenticated.Follow AGENTS.md rather than blindly running the full workspace suite.
cargo build --workspacecargo test -p <crate>cargo test --workspace only when touching mister-smith-core, shared contracts, CI/workflows, or when the issue explicitly requires it.origin:
git push -u origin HEADpull skill, revalidate, and push again.scripts/verify_worktree_closure.sh --fetch --require-upstream --require-sync.branch=$(git branch --show-current)
git push -u origin HEAD
scripts/verify_worktree_closure.sh --fetch --require-upstream --require-sync
pr_state=$(gh pr view --json state -q .state 2>/dev/null || true)
if [ -z "$pr_state" ]; then
gh pr create --title "<clear title>" --body-file /tmp/pr_body.md
else
gh pr edit --title "<clear title>" --body-file /tmp/pr_body.md
fi
gh pr view --json url -q .url