Run any Skill in Manus with one click

codex-pair-resume

Stars12

Forks6

UpdatedJuly 2, 2026 at 20:17

Resume the codex-pair PostToolUse hook for this project after a previous /codex-pair-pause. Removes the .codex-pair/state/paused sentinel. The hook starts reviewing edits again on the next Edit/Write/MultiEdit. No-op if no pause sentinel exists.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

Lykhoyda

Lykhoyda/ask-llm

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Computer Occupations, All OtherComputer and Mathematical Occupations·SOC 15-1299

SKILL.md

readonly

name	codex-pair-resume
description	Resume the codex-pair PostToolUse hook for this project after a previous /codex-pair-pause. Removes the .codex-pair/state/paused sentinel. The hook starts reviewing edits again on the next Edit/Write/MultiEdit. No-op if no pause sentinel exists.
user_invocable	true

Resume codex-pair for this project

Removes the pause sentinel written by /codex-pair-pause, restoring normal codex-pair review behavior. The .codex-pair/context.md marker and .codex-pair/state/ directory are left in place (the directory holds the cache, inflight locks, and any other future state per ADR-092).

Instructions

Locate the .codex-pair/context.md marker by walking up from the current working directory (the project ROOT is the directory holding .codex-pair/). If no marker is found, inform the user: "codex-pair is not enabled in this project (no .codex-pair/context.md marker found). Nothing to resume."
Check whether the pause sentinel exists at <marker-dir>/.codex-pair/state/paused:
- If it does not exist, tell the user: "codex-pair was not paused — no .codex-pair/state/paused sentinel found. No change."
- If it exists and is non-empty, it is an auto-pause written by the hook itself (quota exhaustion or repeated failures — see #176). cat it and show the user the kind, reason, and resetHint fields before removing, so they know whether the provider has likely recovered.
- Remove it, together with the consecutive-failure counter — resuming while the counter is still at threshold would re-pause on the very next single failure. Quote the paths so marker directories with spaces work:
```
rm -f -- "<marker-dir>/.codex-pair/state/paused" "<marker-dir>/.codex-pair/state/failures.json"
```

Confirm to the user with the marker directory path:

codex-pair resumed for <marker-dir>
The next Edit/Write/MultiEdit will trigger a review.

More from this repository

same repository

sol-review

Lykhoyda/ask-llm

Review the current code changes specifically with OpenAI GPT-5.6 Sol. Use when the user asks for a Sol review, says "review with Sol", wants a model-pinned Codex review, or invokes /sol-review.

2026-07-1712

codex-image

Lykhoyda/ask-llm

Generate an image via OpenAI's gpt-image-2 model through the Codex CLI. Use when user asks to "generate an image", "create an image", "make a picture of", "render a graphic", "draw something", or wants visual content via Codex. Requires codex-cli >= 0.125.0 with the `image_generation` feature flag enabled (stable + on-by-default since 0.125).

2026-07-1712

compare

Lykhoyda/ask-llm

This skill should be used when the user asks to "compare LLMs", "see how each provider answers", "side-by-side response", "what do Gemini, Codex, Ollama, and Antigravity think", or wants raw responses from multiple providers without synthesis. Unlike /brainstorm (which synthesizes findings) or /multi-review (which validates code reviews), /compare just shows each provider's answer side-by-side.

2026-07-1712

antigravity-review

Lykhoyda/ask-llm

Get a second opinion from Google Antigravity (agy) on your current code changes. Analyzes staged/unstaged diffs and returns prioritized findings. Use when the user asks to "review with Antigravity", "Antigravity code review", or "ask agy to check my code".

2026-07-1412

codex-pair

Lykhoyda/ask-llm

Show codex-pair status and set up the per-edit Codex review hook for this project. Detects whether codex-pair is active, paused, or not yet configured. On first run (no marker), offers interactive setup with auto-detected project context. On subsequent runs, shows current state, recent review activity, and toggle instructions. The per-edit hook itself runs automatically; this command is the human-facing dashboard for it.

2026-07-1412

fable-review

Lykhoyda/ask-llm

Request a review of the current code changes from the Fable model. Use when the user asks for a Fable review, says "review with Fable", wants Fable's independent perspective on a diff, or invokes /fable-review.

2026-07-1412

name	codex-pair-resume
description	Resume the codex-pair PostToolUse hook for this project after a previous /codex-pair-pause. Removes the .codex-pair/state/paused sentinel. The hook starts reviewing edits again on the next Edit/Write/MultiEdit. No-op if no pause sentinel exists.
user_invocable	true

Resume codex-pair for this project

Instructions

Locate the .codex-pair/context.md marker by walking up from the current working directory (the project ROOT is the directory holding .codex-pair/). If no marker is found, inform the user: "codex-pair is not enabled in this project (no .codex-pair/context.md marker found). Nothing to resume."
Check whether the pause sentinel exists at <marker-dir>/.codex-pair/state/paused:
- If it does not exist, tell the user: "codex-pair was not paused — no .codex-pair/state/paused sentinel found. No change."
- If it exists and is non-empty, it is an auto-pause written by the hook itself (quota exhaustion or repeated failures — see #176). cat it and show the user the kind, reason, and resetHint fields before removing, so they know whether the provider has likely recovered.
- Remove it, together with the consecutive-failure counter — resuming while the counter is still at threshold would re-pause on the very next single failure. Quote the paths so marker directories with spaces work:
```
rm -f -- "<marker-dir>/.codex-pair/state/paused" "<marker-dir>/.codex-pair/state/failures.json"
```

Confirm to the user with the marker directory path:

codex-pair resumed for <marker-dir>
The next Edit/Write/MultiEdit will trigger a review.