ワンクリックでManusで任意のスキルを実行

codex-cancel

スター48

フォーク5

更新日2026年6月21日 13:19

Cancel an active background Codex job. Use when asked "codex cancel", "stop codex", "abort the codex job", or wants to stop a running Codex task.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

LeeJuOh

LeeJuOh/claude-code-zero

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

Codex Job Cancel

Pass-through wrapper around the Official Codex companion's cancel subcommand. Exists so users who disabled the Official plugin's slash commands can still cancel jobs via codex-advisor.

Phase 1: Confirm target (if ambiguous)

If the user did not provide a job-id, the companion cancels the most recent active job — which may not be what they intended. Use AskUserQuestion when:

Multiple active jobs exist (check via node "$CODEX_COMPANION" status first, optional).
The user's phrasing suggests a specific job ("cancel the rescue", "stop the research") but no ID.

Skip the prompt when the intent is obvious (single active job, or they pass an explicit ID).

Phase 2: Invoke companion cancel

set -o pipefail
CODEX_COMPANION=$("${CLAUDE_PLUGIN_ROOT}/scripts/resolve-companion.sh") \
  || { echo "Official Codex plugin not found — run /codex-setup" >&2; exit 1; }

node "$CODEX_COMPANION" cancel $ARGUMENTS

Relay the companion's output verbatim. It typically reports cancelled or no-op (not running).

Gotchas

Cancellation is not instant. The companion signals the Codex worker; in-flight tool calls may complete before the worker exits. Don't promise "stopped immediately".
Cancelling a rescue job does NOT revert the diff. If Codex already wrote files under --write, those changes stay on disk. Remind the user to git diff / git restore if needed.
No job-id == most recent active. Only one job at a time is the common case, so this usually does what the user wants — but with multiple active jobs it can surprise. When in doubt, run status first and cancel by explicit ID.

このリポジトリの他の Skills

同じリポジトリ

worktree-setup

LeeJuOh/claude-code-zero

Set up worktree-plus for a repo — manage git config (baseBranch, branchPrefix, dirBase, guessRemote) and build the .worktreeinclude / .worktreelink files by scanning which gitignored files actually exist. Use when the user asks to set up or configure worktree-plus, view or change worktree settings, reset the plugin config, or decide which gitignored files should be copied or symlinked into new worktrees.

2026-07-1748

codex-rescue

LeeJuOh/claude-code-zero

Delegate an implementation task to Codex, then Claude reviews the result. Use when asked "codex rescue", "delegate to codex", "have codex do it", or wants Codex to implement or fix something.

2026-07-1748

codex-setup

LeeJuOh/claude-code-zero

Check Codex CLI, auth, Official plugin status, and configure defaults. Use when asked "codex setup", "configure codex", "install codex", or when another codex-advisor skill reports setup issues.

2026-07-1748

context-health-visual

LeeJuOh/claude-code-zero

Diagnose Claude Code environment health — context budget, description obesity, trigger collisions, hooks, MCP, plugins, CLAUDE.md, memory, and skill-security scan. Use when asked to audit the environment, check context budget, review plugins, or scan installed skills for risky patterns.

2026-07-1748

diff-visual

LeeJuOh/claude-code-zero

Visualize git diffs as interactive HTML reports with architecture diagrams, change analysis, and side-by-side split-diff of the actual changed code. Use when asked to visualize, review, or summarize a diff, branch, commit, or PR — including seeing the real changed lines, not just a summary. Accepts branch names, commit hashes, HEAD, PR numbers, or commit ranges.

2026-07-1748

doc-visual

LeeJuOh/claude-code-zero

Convert any markdown document into a diagram-enriched visual HTML report. Use when asked to visualize, illustrate, or create a visual report from a document with diagrams. Single md file input. Also trigger when: "make this document visual", "add diagrams to this doc", "turn this markdown into a report", "visualize this README/ADR/spec", or any request to render a document with embedded diagrams.

2026-07-1748

name	codex-cancel
description	Cancel an active background Codex job. Use when asked "codex cancel", "stop codex", "abort the codex job", or wants to stop a running Codex task.
argument-hint	[job-id]
allowed-tools	["Bash","AskUserQuestion"]

Codex Job Cancel

Pass-through wrapper around the Official Codex companion's cancel subcommand. Exists so users who disabled the Official plugin's slash commands can still cancel jobs via codex-advisor.

Phase 1: Confirm target (if ambiguous)

If the user did not provide a job-id, the companion cancels the most recent active job — which may not be what they intended. Use AskUserQuestion when:

Multiple active jobs exist (check via node "$CODEX_COMPANION" status first, optional).
The user's phrasing suggests a specific job ("cancel the rescue", "stop the research") but no ID.

Skip the prompt when the intent is obvious (single active job, or they pass an explicit ID).

Phase 2: Invoke companion cancel

set -o pipefail
CODEX_COMPANION=$("${CLAUDE_PLUGIN_ROOT}/scripts/resolve-companion.sh") \
  || { echo "Official Codex plugin not found — run /codex-setup" >&2; exit 1; }

node "$CODEX_COMPANION" cancel $ARGUMENTS

Relay the companion's output verbatim. It typically reports cancelled or no-op (not running).

Gotchas

Cancellation is not instant. The companion signals the Codex worker; in-flight tool calls may complete before the worker exits. Don't promise "stopped immediately".
Cancelling a rescue job does NOT revert the diff. If Codex already wrote files under --write, those changes stay on disk. Remind the user to git diff / git restore if needed.
No job-id == most recent active. Only one job at a time is the common case, so this usually does what the user wants — but with multiple active jobs it can surprise. When in doubt, run status first and cancel by explicit ID.