Explicit-only workflow that writes a redacted continuation handoff to a unique temporary Markdown file. Use only when the user explicitly asks for a handoff for another session.
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
When writing is allowed, write exactly one uniquely named Markdown file under $TMPDIR when set, otherwise /tmp; never write the handoff in the repository. Use a collision-resistant name such as codex-handoff-<timestamp>-<random>.md. When writing is forbidden, render the complete handoff in chat and create no file. Report the absolute path when a file is written and do not automatically start a new session.
Include the next-session focus, repository path, branch and HEAD, working-tree status, objective, settled decisions, relevant artifacts by path or URL, completed verification, blockers, exact next actions, and remaining authorization boundaries. If the user supplied a next-session focus, tailor the document to it.
Recommend only relevant Skills that are actually available in the current environment. Do not duplicate full plans, diffs, or other existing artifacts; reference them instead.
Redact secrets, credentials, passwords, tokens, personally identifiable information, and user content that is not needed for continuation.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Read public X/Twitter post URLs as structured evidence through the ADHX API. Use for relevant user-provided or research-discovered x.com, twitter.com, or adhx.com links. ADHX does not search X, and long-form Article content may be incomplete.
日本語の概要は準備中です。原文の説明を表示しています。
Shared vocabulary for designing deep modules, interfaces, seams, adapters, leverage, and locality. Use when designing or reshaping module boundaries, making code more testable, or evaluating interface depth.
日本語の概要は準備中です。原文の説明を表示しています。
Disciplined diagnosis loop for hard bugs, regressions, flaky failures, and performance problems with unclear cause. Use for root-cause debugging after a concrete symptom exists; do not use for routine implementation or speculative cleanup.
日本語の概要は準備中です。原文の説明を表示しています。
Route requests for current library, framework, SDK, API, CLI, or cloud-service documentation through available documentation tools and primary sources.
日本語の概要は準備中です。原文の説明を表示しています。
Build and sharpen a project's domain model. Use only when actively changing glossary or ubiquitous-language terms, or recording a durable architectural decision; merely reading a glossary is not a trigger.
日本語の概要は準備中です。原文の説明を表示しています。
Explicit-only interview loop for stress-testing a plan, decision, or idea. Use only when the user asks to grill, interrogate, interview, or stress-test their thinking before action.
日本語の概要は準備中です。原文の説明を表示しています。