Skip to content

Conversation

@varunr89
Copy link

@varunr89 varunr89 commented Dec 5, 2025

Summary
Documented how to use native Codex skills instead of the legacy superpowers
hook: enable [features] skills = true, store SKILLs in ~/.codex/skills,
restart, and note that hooks.json isn’t consumed by Codex.

Motivation and Context

The old superpowers hook path (~/.config/superpowers/skills + hooks.json)
isn’t read by Codex. The native skills feature now discovers skills directly
from ~/.codex/skills, so users need clear migration guidance.

How Has This Been Tested?

Manually verified on macOS with Codex CLI:

  • Placed skills in ~/.codex/skills.
  • Enabled [features] skills = true in ~/.codex/config.toml.
  • Restarted Codex and confirmed the skills list appears on new sessions.
    Also validated the session-start hook script runs when invoked directly
    (for optional custom messaging).

Breaking Changes

No code break, but configuration change required: users must enable
[features] skills = true and place skills in ~/.codex/skills (legacy
superpowers path is ignored).

Types of changes

  • Bug fix
  • New feature
  • Breaking change
  • Documentation update

Checklist

  • 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

Hooks (~/.codex/hooks/hooks.json) aren’t consumed by the Codex CLI; use
them only for optional custom messaging. The native skills discovery is the
supported path.

Summary by CodeRabbit

  • Documentation
    • Added user guide for native skills support: setup, organization, and enabling the feature.
    • Describes activation workflow (requires restarting and starting a new session) and how skills are discovered and listed in-session.
    • Includes migration guidance from the legacy skills integration and notes about optional custom session messaging.

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

Document the transition from legacy superpowers to native skills support in Codex.
@coderabbitai
Copy link

coderabbitai bot commented Dec 5, 2025

Warning

Rate limit exceeded

@varunr89 has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 13 minutes and 20 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between ee74f5e and 6a42c24.

📒 Files selected for processing (1)
  • .codex/Update.md (1 hunks)

Walkthrough

A new documentation file .codex/Update.md is added that describes migrating to Codex native skills support, directory layout for skills, enabling the feature via ~/.codex/config.toml, runtime lifecycle notes, discovery behavior, and guidance for moving items from the legacy Superpowers path.

Changes

Cohort / File(s) Summary
Skills transition documentation
\.codex/Update.md
Added new guide detailing Codex native skills support: place skills under ~/.codex/skills (one folder per skill with SKILL.md), enable with [features] skills = true in ~/.codex/config.toml, restart CLI/new session to see a “## Skills” block, discovery occurs without hooks, session-start.sh is optional for messaging, and migrate useful items from ~/.config/superpowers/skills.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

  • Documentation-only change; no code or public API modifications.
  • Review focus: clarity and accuracy of migration/config instructions.

Poem

I hop through folders, tidy and spry,
.codex/Update.md under moonlit sky,
Skills lined up in neat little rows,
A new config switch, and off everybody goes,
Happy hops — the migration's a try! 🐇✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The pull request title accurately summarizes the main change—adding documentation for native Codex skills support and migration guidance from the legacy superpowers integration.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

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.

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: 3

🧹 Nitpick comments (1)
.codex/Update.md (1)

15-16: Format "Notes" as a heading for consistency.

The section uses plain text instead of markdown heading syntax. For consistency with the rest of the document, format it as # Notes.

-Notes
+# Notes
📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 154d664 and 08d2e07.

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

6-6: No space after hash on atx style heading

(MD018, no-missing-space-atx)


9-9: Fenced code blocks should have a language specified

(MD040, fenced-code-language)

varunr89 and others added 2 commits December 5, 2025 07:58
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
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: 0

🧹 Nitpick comments (2)
.codex/Update.md (2)

3-4: Convert bare URL to markdown link format.

The URL should use markdown link syntax for better readability and to comply with markdown linting standards.

-With the introduction of native support for skills in codex (https://github.com/
-  openai/codex/blob/main/docs/skills.md), we don't have to use legacy superpowers hook.
+With the introduction of native support for skills in [Codex](https://github.com/
+  openai/codex/blob/main/docs/skills.md), we don't have to use legacy superpowers hook.

9-12: Specify language for code block.

Add toml to the code fence for proper syntax highlighting and compliance with markdown linting standards.

    2) Enable feature: add to `~/.codex/config.toml`:
-   ```
+   ```toml
    [features]
    skills = true
    ```
📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 08d2e07 and ee74f5e.

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

3-3: Bare URL used

(MD034, no-bare-urls)


9-9: Fenced code blocks should have a language specified

(MD040, fenced-code-language)

🔇 Additional comments (1)
.codex/Update.md (1)

1-17: Well-structured migration guide.

The documentation clearly outlines the steps for adopting Codex native skills, addresses the legacy superpowers path, and provides helpful lifecycle notes. The guidance is practical and aligns well with the PR objectives.

Corrected code block formatting in update instructions.
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.

1 participant