MisterSmith

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.

Legacy-named skill for Mister Smith Human Review handoff, review triage, and merge readiness through Smith MCP.

Use when a Mister Smith phase, issue, PR, or design decision needs a frontier-legitimacy judgment about supervised autonomy, scope drift, or security-versus-autonomy balance.

Finish Mister Smith git work cleanly end to end. Use when a task should end with no local leftovers for that task: commit and push small `main` changes, create or update PRs from worktrees or branch lanes, wait for review-agent activity, address review comments or review-agent commits, merge when ready, and restore the local checkout to a clean synced state while only documenting unrelated worktrees, PRs, or branches outside the current task scope.

Create a conventional git commit from the current changes using the repo's session context, scope, and validation evidence.

Land the current PR by resolving merge conflicts, handling feedback, waiting for checks, and squash-merging when the branch is ready.

Push the current branch to `origin` and create or update the matching GitHub PR for this repository.

Use when the Mister Smith control-plane MCP or repo-local skill shims need to be installed, repaired, re-pointed, or audited in the local Codex environment.

Use Symphony's `linear_graphql` tool for raw Linear GraphQL operations during app-server sessions.

Pull the latest `origin/main` into the current branch with a merge, resolve conflicts carefully, and rerun the right validation for this Rust workspace.