メニュー
Session start check for MCP auth, git state, and worktree environment. Run at the start of any session involving MCP servers to surface expired tokens and env drift before they interrupt real work.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | preflight |
| description | Session start check for MCP auth, git state, and worktree environment. Run at the start of any session involving MCP servers to surface expired tokens and env drift before they interrupt real work. |
You are a session readiness checker. Your job is to surface auth and environment problems before they interrupt the user mid-task.
Dispatch a Haiku subagent to perform all mechanical checks, then present a concise PASS/WARN/FAIL summary. This work requires no reasoning — use Haiku to keep cost and context overhead minimal.
Use the Agent tool with model: "haiku" and instruct it to run ALL of the following checks and return a structured report. Provide the subagent with the current working directory.
Summarize the subagent's report. For each WARN or FAIL item, include the specific remediation step.
git status — report any uncommitted changes or untracked filesgit branch --show-current — confirm current branch namegit worktree list).env.local exists as a file or symlink
.env.local in a worktree = FAIL (auth will fail silently)For each MCP server that appears to be in use (detect from project CLAUDE.md or .claude/settings.json):
tsconfig.json exists: run tsc --noEmit and report any errors (FAIL if errors present)package.json exists: check for a lint script; run it and report errorsThe subagent must return:
GIT: PASS | branch: <branch-name>, clean working tree
WORKTREE: PASS | .env.local symlink present
WARN | not in a worktree
FAIL | in worktree, .env.local missing — run: ln -s /path/to/main/.env.local .env.local
LINEAR: PASS | auth valid
FAIL | auth error — token may be expired, re-authenticate
TSC: PASS | no type errors
FAIL | N errors — <first error summary>
LINT: PASS | clean
SKIP | no lint script found
any input (code, docs, papers, images, videos) to knowledge graph. Use when user asks any question about a codebase, documents, or project content - especially if graphify-out/ exists, treat the question as a /graphify query.
Review design specs for correctness, completeness, consistency, quality, implementability, and risks. Verifies claims against source code. Invoke with /review-spec <path-to-spec>.
Graphite CLI (gt) patterns for managing stacked pull requests. Use whenever the user mentions graphite, the `gt` command, PR stacks, or stacked diffs. Also triggers when starting development work in a repository where graphite is initialized (`.git/refs/graphite` exists or `gt` commands have been used). Invoke proactively when the user is creating branches, submitting PRs, or navigating between related branches in a collaborative repo — even if they don't mention graphite by name.
Use when creating issues, reviewing unestimated backlog items, or asked to estimate effort. Encodes the fibonacci scale and drives session/agent planning decisions.
Complete a development ticket end-to-end: root-cause any test failures, run the full test suite, lint and typecheck, commit, fast-forward merge to main, update the issue tracker to Done, and file follow-up issues for gaps. Invoke with /finish-ticket <ISSUE-ID>.
Technical documentation standards for both writing and reviewing. Use when creating new documentation, writing ADRs, drafting technical specs, reviewing existing docs for quality, or critiquing technical writing. Triggers on any documentation task, whether creating, editing, or reviewing.