Name: rescue
Author: xiaodream551-a11y

Prompt file imported from xiaodream551-a11y/revitcli (.codex/prompts/rescue.md). Copyright stays with the author.

Rescue turn

Build or tests are red. The combined build + test log appears above this section. Your job is root cause + minimal honest fix, in one commit.

Required reading

.codex/state/last-build.log and .codex/state/last-test.log (already in context).
git diff HEAD~1..HEAD if a previous commit exists, otherwise git diff --staged.
The active feature md (path is in .codex/state/current-feature.txt).

Allowed actions

Read the stack trace, identify the actual cause, write the minimal fix.
Fix mis-quoted JSON expectations, wrong path separators, missing await, null reference paths, regex overspecification.
Adjust a test whose assertion was tied to unstable formatting (timestamp, random order) to use a stable substring or property check — but the test must still verify the original intent.

Commit the fix. Body ends with:

Root cause: <one sentence>
Verify: <single shell command that now passes>

Forbidden (these are the patterns that make CI dishonest)

Adding [Skip], [SkippedOnLinuxCI], [Trait("skip","true")], or any conditional that disables a failing test.
Replacing an assertion with Assert.True(true) or weakening expectations to fit the current (wrong) output.
Wrapping failing code in if (false) { ... } or commenting it out.
Using --filter "FullyQualifiedName!~<failing test>" to bypass.
Deleting a failing test rather than fixing the code.
catch { } / catch (Exception) { } with no rethrow.
Reverting the parent worker's entire diff to "make it go away" unless you are confident the worker's approach is wrong AND you write a Notes line stating why.

Escape valve

If the failure is genuinely out of this environment's reach (requires Revit + Windows, or depends on a service that doesn't exist yet), leave HEAD unchanged. Set the feature status: blocked and add a Notes line:

Blocked: <failing test or build error>.
Requires: <environment / next missing piece>.
Hypothesis: <your best guess at root cause>.

Retry cap

The tick script tracks rescue attempts per checkbox. If you can see (from .codex/state/last-tick.md) that this is your SECOND rescue on the same checkbox and you still cannot fix it honestly, set status: blocked and exit. The third rescue is not allowed.

Install rescue and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

# Rescue turn Build or tests are red. The combined build + test log appears above this section. Your job is **root cause + minimal honest fix**, in one commit. ## Required reading - `.codex/state/last-build.log` and `.codex/state/last-test.log` (already in context). - `git diff HEAD~1..HEAD` if a previous commit exists, otherwise `git diff --staged`. - The active feature md (path is in `.codex/state/current-feature.txt`). ## Allowed actions - Read the stack trace, identify the actual cause, write the minimal fix. - Fix mis-quoted JSON expectations, wrong path separators, missing `await`, null reference paths, regex overspecification. - Adjust a test whose assertion was tied to unstable formatting (timestamp, random order) to use a stable substring or property check — but the test must still verify the original intent. - Commit the fix. Body ends with: ``` Root cause: <one sentence> Verify: <single shell command that now passes> ``` ## Forbidden (these are the patterns that make CI dishonest) - Adding `[Skip]`, `[SkippedOnLinuxCI]`, `[Trait("skip","true")]`, or any conditional that disables a failing test. - Replacing an assertion with `Assert.True(true)` or weakening expectations to fit the current (wrong) output. - Wrapping failing code in `if (false) { ... }` or commenting it out. - Using `--filter "FullyQualifiedName!~<failing test>"` to bypass. - Deleting a failing test rather than fixing the code. - `catch { }` / `catch (Exception) { }` with no rethrow. - Reverting the parent worker's entire diff to "make it go away" unless you are confident the worker's approach is wrong AND you write a Notes line stating why. ## Escape valve If the failure is genuinely out of this environment's reach (requires Revit + Windows, or depends on a service that doesn't exist yet), leave HEAD unchanged. Set the feature `status: blocked` and add a Notes line: ``` Blocked: <failing test or build error>. Requires: <environment / next missing piece>. Hypothesis: <your best guess at root cause>. ``` ## Retry cap The tick script tracks rescue attempts per checkbox. If you can see (from `.codex/state/last-tick.md`) that this is your SECOND rescue on the same checkbox and you still cannot fix it honestly, set `status: blocked` and exit. The third rescue is not allowed.

{ "prompt": "# Rescue turn\n\nBuild or tests are red. The combined build + test log appears above this\nsection. Your job is **root cause + minimal honest fix**, in one commit.\n\n## Required reading\n\n- `.codex/state/last-build.log` and `.codex/state/last-test.log` (already in\n context).\n- `git diff HEAD~1..HEAD` if a previous commit exists, otherwise\n `git diff --staged`.\n- The active feature md (path is in `.codex/state/current-feature.txt`).\n\n## Allowed actions\n\n- Read the stack trace, identify the actual cause, write the minimal fix.\n- Fix mis-quoted JSON expectations, wrong path separators, missing `await`,\n null reference paths, regex overspecification.\n- Adjust a test whose assertion was tied to unstable formatting (timestamp,\n random order) to use a stable substring or property check — but the test\n must still verify the original intent.\n- Commit the fix. Body ends with:\n ```\n Root cause: <one sentence>\n Verify: <single shell command that now passes>\n ```\n\n## Forbidden (these are the patterns that make CI dishonest)\n\n- Adding `[Skip]`, `[SkippedOnLinuxCI]`, `[Trait(\"skip\",\"true\")]`, or any\n conditional that disables a failing test.\n- Replacing an assertion with `Assert.True(true)` or weakening expectations\n to fit the current (wrong) output.\n- Wrapping failing code in `if (false) { ... }` or commenting it out.\n- Using `--filter \"FullyQualifiedName!~<failing test>\"` to bypass.\n- Deleting a failing test rather than fixing the code.\n- `catch { }` / `catch (Exception) { }` with no rethrow.\n- Reverting the parent worker's entire diff to \"make it go away\" unless you\n are confident the worker's approach is wrong AND you write a Notes line\n stating why.\n\n## Escape valve\n\nIf the failure is genuinely out of this environment's reach (requires\nRevit + Windows, or depends on a service that doesn't exist yet), leave\nHEAD unchanged. Set the feature `status: blocked` and add a Notes line:\n\n```\nBlocked: <failing test or build error>.\nRequires: <environment / next missing piece>.\nHypothesis: <your best guess at root cause>.\n```\n\n## Retry cap\n\nThe tick script tracks rescue attempts per checkbox. If you can see (from\n`.codex/state/last-tick.md`) that this is your SECOND rescue on the same\ncheckbox and you still cannot fix it honestly, set `status: blocked` and\nexit. The third rescue is not allowed.", "variables": [], "notes": "Build or tests are red. The combined build + test log appears above this section. Your job is **root cause + minimal honest fix**, in one commit.", "metadata": { "source": { "provider": "github-codex-prompts", "repository": "https://github.com/xiaodream551-a11y/revitcli", "path": ".codex/prompts/rescue.md", "ref": "38ff854afa5948758836fbe9cb6b35b5a1fe0b80", "url": "https://github.com/xiaodream551-a11y/revitcli/blob/38ff854afa5948758836fbe9cb6b35b5a1fe0b80/.codex/prompts/rescue.md", "key": "xiaodream551-a11y/revitcli/.codex/prompts/rescue.md" } } }

rescue

About

Rescue turn

Required reading

Allowed actions

Forbidden (these are the patterns that make CI dishonest)

Escape valve

Retry cap

Install rescue and it becomes one more candidate the router can pick - when it fits.

Use it

Manifest

Reviews