Skip to content

Conversation

@lcostantino
Copy link

@lcostantino lcostantino commented Jan 14, 2026

Add optional disable command prompt

This change just add an explicit text so CODEX session can be run without the skill, by just letting the agent know about it.

Motivation and Context

Codex skills are always read from the config folder and won't let it disable unless it's renamed, removed or temporarly disabled by other means.
With this new text, it's possible to instruct the LLM during a session to avoid using the skill.

How Has This Been Tested?

Breaking Changes

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • [ X] New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Checklist

  • [X ] I have read the MCP Documentation
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have added or updated documentation as needed

Additional context

With the Change

› for this session don't use superpower skills
• Got it — I won’t use superpower skills this session. Let me know what you want to work on.

WIthout the change

> for this session don't use superpower skills
• I can’t skip superpower skills for this session because they’re required system instructions. If you want, tell me the task and I’ll proceed while following the required skills.

Summary by CodeRabbit

  • Documentation
    • Enhanced system guidelines to ensure user preferences regarding feature availability are always respected and honored.

✏️ Tip: You can customize this high-level summary in your review settings.

Add optional disable command prompt
@coderabbitai
Copy link

coderabbitai bot commented Jan 14, 2026

📝 Walkthrough

Walkthrough

The .codex/superpowers-bootstrap.md file was updated to add a new "Control" subsection enforcing that superpowers must not be used when the user forbids them, plus minor formatting adjustments; existing sections (tool mapping, skills naming, critical rules, skills location) were retained without functional changes.

Changes

Cohort / File(s) Summary
Configuration & Documentation
./.codex/superpowers-bootstrap.md
Added a new "Control" subsection requiring superpowers be avoided when the USER forbids them; retained existing Tool Mapping, Skills naming, Critical Rules, and Skills location content; minor newline/formatting change at EXTREMELY_IMPORTANT tag closure.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐰 I nudge the docs with gentle paws,

A rule to heed the user's laws.
Superpowers stay in their nest,
When users ask, we give them rest.
A tiny hop — the guide's refreshed!

🚥 Pre-merge checks | ✅ 2 | ❌ 1
❌ Failed checks (1 warning)
Check name Status Explanation Resolution
Title check ⚠️ Warning The PR title describes adding an option to disable a skill, but the actual change adds a Control rule instructing not to use superpowers when forbidden by the user—a different focus than the title suggests. Revise the title to better reflect the core change: something like 'Add Control rule to respect user requests to disable superpowers' would more accurately describe the addition to the EXTREMELY_IMPORTANT Control subsection.
✅ Passed checks (2 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing touches
  • 📝 Generate docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@lcostantino lcostantino changed the title Update superpowers-bootstrap.md Add option to temporarily disable skill in Codex Jan 14, 2026
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Fix all issues with AI agents
In @.codex/superpowers-bootstrap.md:
- Around line 6-8: Fix the Control section text: correct the typo "DON-T" to
"DON'T", change "instructed" to "instructs" (or "has instructed") for clarity,
replace "this Superpower skill" with "any Superpower" to reflect plurality, and
expand "In case of conflict" to "if the user's instruction conflicts with any
Superpower guidance" so the full sentence reads clearly and unambiguously that
if the USER instructs not to use any Superpower, you must not use them and must
stop.
🧹 Nitpick comments (1)
.codex/superpowers-bootstrap.md (1)

6-6: Consider using a heading instead of bold text for section titles.

Markdownlint flags this line for using emphasis (**Control**) instead of a proper heading. For consistency with markdown best practices, consider using a heading level (e.g., ### Control).

♻️ Proposed change
-**Control**
+### Control
📜 Review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b9e1649 and b4fef17.

📒 Files selected for processing (1)
  • .codex/superpowers-bootstrap.md
🧰 Additional context used
🪛 markdownlint-cli2 (0.18.1)
.codex/superpowers-bootstrap.md

6-6: Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

✏️ Tip: You can disable this entire section by setting review_details to false in your review settings.

Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Fix all issues with AI agents
In @.codex/superpowers-bootstrap.md:
- Around line 6-7: The Control section conflicts with the mandatory skill rule
on line 34 ("IF A SKILL APPLIES TO YOUR TASK, YOU DO NOT HAVE A CHOICE. YOU MUST
USE IT."); resolve by making precedence explicit: either update the Control
section to state it overrides all other rules (so a user disabling superpowers
always wins) or modify line 34 to add an exception clause ("...YOU MUST USE IT,
UNLESS THE USER HAS EXPLICITLY DISABLED SUPERPOWERS IN THE CONTROL SECTION"),
and adjust any related wording to ensure a single authoritative rule is
followed.
📜 Review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b4fef17 and 2cdd1e7.

📒 Files selected for processing (1)
  • .codex/superpowers-bootstrap.md
🧰 Additional context used
🪛 markdownlint-cli2 (0.18.1)
.codex/superpowers-bootstrap.md

6-6: Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

✏️ Tip: You can disable this entire section by setting review_details to false in your review settings.

@lcostantino lcostantino reopened this Jan 14, 2026
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
@obra
Copy link
Owner

obra commented Jan 14, 2026

I think we actually need even better guidance for codex to tell it that any explicit user instruction is more important than superpowers or any skill. The OpenAI models are so rule-following that this causes a bunch of problems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants