[auto] cat-mode: say it applies by default behind CATSTACK_CAT_MODE_DEFAULT

[EdbertChan]

The cat-mode-default hook applies this skill on every investigation or
execution prompt when CATSTACK_CAT_MODE_DEFAULT=1. Name that in the skill
body so a reader of the skill knows why it applied without being typed,
and keep disable-model-invocation: true. Lock it with a test.

Co-Authored-By: Claude Fable 5.1 noreply@anthropic.com
Claude-Session: https://claude.ai/code/session_019CoNSA1EKhBHfVUX7feoKR

---

Note

Low Risk
Documentation and structural regression tests only; no hook or runtime behavior changes.

Overview
The cat-mode skill intro now states that conventions apply by default when CATSTACK_CAT_MODE_DEFAULT=1, injected by the cat-mode-default hook—so readers understand auto-application without a typed /cat-mode. Frontmatter disable-model-invocation: true is unchanged.

Tests add TestCatModeDefaultHookPointer to lock that prose, confirm engine/hooks/cat-mode-default exists, and keep disable-model-invocation true. cat-mode-default is allowlisted in the skill-reference checker so the hook name in backticks is not treated as a missing skill.

^{Reviewed by Cursor Bugbot for commit 14bd122. Bugbot is set up for automated code reviews on this repo. Configure here.}

[EdbertChan]

This pull request is part of a Mergify stack:

#	Pull Request	Link
1	[auto] hook: cat-mode-default applies cat-mode on work turns behind an env flag	#247
2	[auto] cat-mode: say it applies by default behind CATSTACK_CAT_MODE_DEFAULT	#248	👈

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_71e32fe3-2552-4d01-bfa8-fca6718af0af)

[EdbertChan]

@Mergifyio queue

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-09-07 17:02 UTC · Rule: admin-bypass · triggered by @EdbertChan with the @mergifyio queue command
• ❌ Checks failed · on draft merge queue: checking #248 on main (75540ce) #263
• 🚫 Left the queue — 2026-09-07 17:08 UTC · at 23786ee52d7d166f3b9f0f5db4eca0162186d879

This pull request spent 5 minutes 47 seconds in the queue, including 4 minutes 57 seconds running CI.

Waiting for

• check-success = test

All conditions

• check-success = test
• check-success = lint

Reason

The merge conditions cannot be satisfied due to failing checks

• test

Failing checks:

• ❌ test (job log)

Hint

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio queue comment.

Requeued — the merge queue status continues in this comment ↓.

[EdbertChan]

Revision history

#	Type	Changes	Reason	Date
1	initial	23786ee		2026-09-07 17:13 UTC
2	content	23786ee → fa1a89d		2026-09-07 17:13 UTC
3	content	fa1a89d → 14bd122 (raw)		2026-09-07 17:13 UTC

[EdbertChan]

@Mergifyio queue

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_b017912f-f9e3-426b-87f8-df08f22f61ff)

[EdbertChan]

@Mergifyio queue

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_6e768b1f-a889-4c78-8b92-4fb2f67c8b2c)

[mergify]

queue

☑️ Command queue ignored because it is already running from a previous command.

[mergify]

queue

🛑 The pull request has been removed from the queue admin-bypass

Details

The pull request #248 has been manually updated.

You can take a look at Mergify Merge Queue check runs for more details about the failure.

[EdbertChan]

@Mergifyio queue

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-09-07 17:17 UTC · Rule: admin-bypass · triggered by @EdbertChan with the @mergifyio queue command
• ✅ Checks passed · on draft merge queue: checking #248 on main (3b00bb1), stacked on #238 #270
• ✅ Merged — 2026-09-07 17:24 UTC · at 4589d5b9dcac6c061bf09565e7b0c6ae2599cfd0 · squash

This pull request spent 7 minutes 24 seconds in the queue, including 6 minutes 26 seconds running CI.

Required conditions to merge

• check-success = lint
• check-success = test