メニュー
Record recurring CI failure signatures, successful fixes, rejected fixes, and tool/backend incompatibilities for this repo only. Use after triage, after remediation, or after rejecting an approach so the next iteration does not repeat the same blind fix.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Prepare for a /clear: bring all documentation up to date with this session's changes, persist recovery context (memory + handoff), and emit a copy-paste resume prompt so the next session begins the next task with zero context loss. Invoke explicitly as /clear-prep [next-task].
Use when adding or modifying a devcontainer feature in devcontainer.json - fetch its devcontainer-feature.json schema first and verify every option key exists, because features silently drop unknown options.
Use when creating branches, commits, pushes, or PRs with plain git. Branch BEFORE committing — never commit directly onto the default branch. Avoids virtual-branch composition bugs where commits silently depend on other applied branches.
Write a CROSS-SURFACE session handoff to a tracked path and push it, so a session on another surface (web, desktop, or CLI) can continue with zero context loss. Use when ending a session whose work must be picked up on a DIFFERENT machine/surface. For same-machine /clear continuity use /clear-prep instead. Invoke as /handoff [next-task].
Use when running parallel-scientist research - ALWAYS follow with an opus verification stage that re-probes load-bearing claims and surfaces gaps. Skipping the verifier almost shipped a wrong recommendation in session 2026-04-07e.
Use when sharing a single `~/.ssh/config` across macOS + Linux - apply OpenSSH `IgnoreUnknown` to tolerate macOS-only directives (`UseKeychain`, `AddKeysToAgent`) on Linux where they would otherwise be fatal.
| name | failure-memory |
| description | Record recurring CI failure signatures, successful fixes, rejected fixes, and tool/backend incompatibilities for this repo only. Use after triage, after remediation, or after rejecting an approach so the next iteration does not repeat the same blind fix. |
Store only repo-local, evidence-backed memory for the dotfiles CI workflow.
.omx/state/dotfiles-build-optimizer/failure-memory.jsonl.omx/logs/dotfiles-build-optimizer/Use:
uv run --script plugins/dotfiles-build-optimizer/scripts/record_failure_memory.py \
--input <path-to-report.json>