Skip to content

Conversation

@murphyXu
Copy link

@murphyXu murphyXu commented Jan 19, 2026

Motivation and Context

This change adds a Continue adapter so Continue users can install and invoke Superpowers via slash commands, while reusing the existing skills library structure. It includes:

  • A Continue-specific installer doc (.continue/INSTALL.md)
  • Continue prompt files (.continue/prompts/*.prompt) that show up in Continue’s / menu
  • Root README + detailed docs to make setup discoverable

How Has This Been Tested?

  • Ran bash tests/continue/test-prompts.sh to validate all Continue .prompt files exist and contain required frontmatter (name, description, invokable: true)
  • Validated YAML parsing compatibility for Continue prompt names containing : by quoting name values (prevents YAML parse errors)

Breaking Changes

None. This is a new integration and does not affect existing Claude Code, Codex, or OpenCode implementations.

Types of changes

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

Checklist

  • I have read the https://modelcontextprotocol.io
  • 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

  • Continue prompts use the .prompt extension and superpowers- filename prefix:
    • superpowers-bootstrap.prompt
    • superpowers-brainstorm.prompt
    • superpowers-write-plan.prompt
    • superpowers-execute-plan.prompt
  • Installation is symlink-based:
    • Skills: ~/.continue/skills/superpowers -> ~/.continue/superpowers/skills
    • Prompts: symlink .continue/prompts/*.prompt into ~/.continue/prompts/
  • Continue supports hot loading for skills/prompts; if commands don’t appear immediately, use Continue’s Reload Config.
  • Adds a lightweight repo test (tests/continue/test-prompts.sh) to prevent regressions in prompt frontmatter/paths.

Summary by CodeRabbit

  • Documentation

    • Added comprehensive Continue installation and usage guides and updated the main README with Continue setup instructions
  • New Prompts

    • Added invokable Superpowers prompts for brainstorming, planning, executing, and bootstrapping workflows
  • Tests

    • Added a validation script to verify prompt frontmatter and presence
  • Chores

    • Updated ignore patterns to exclude macOS metadata files (.DS_Store)

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

@coderabbitai
Copy link

coderabbitai bot commented Jan 19, 2026

📝 Walkthrough

Walkthrough

Adds Continue integration materials: installation docs, four invokable Superpowers prompts, a prompt-validation test script, and a .gitignore entry. Changes are documentation and prompts only; no code or exported API changes.

Changes

Cohort / File(s) Summary
Continue Setup Documentation
docs/README.continue.md, .continue/INSTALL.md
New installation and usage guides covering directory layout, symlink usage for skills/prompts, manual and quick install flows, verification commands, and update instructions.
Continue Prompts
.continue/prompts/superpowers-bootstrap.prompt, .continue/prompts/superpowers-brainstorm.prompt, .continue/prompts/superpowers-execute-plan.prompt, .continue/prompts/superpowers-write-plan.prompt
Four new invokable prompt files with YAML frontmatter (name, description, invokable) and invocation instructions; bootstrap prompt adds skill-discovery, invocation conventions, and tool-mapping guidance.
Project Documentation Update
README.md
Added a "Continue" section referencing .continue/INSTALL.md and docs/README.continue.md.
Configuration & Testing
.gitignore, tests/continue/test-prompts.sh
Added .DS_Store to .gitignore; new test script validates existence and frontmatter structure of .continue/prompts files and exits with descriptive errors on failure.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

Poem

🐰 Hoppity-hop, new prompts appear,

Bootstrap, brainstorm, plans draw near,
Symlinks snug in folders bright,
Tests check frontmatter through the night,
Superpowers ready — take flight! ✨

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The PR title 'feat: Add Continue integration' directly and clearly summarizes the main change—adding Continue integration to the project with new installer documentation, prompt files, and setup instructions.
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.

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 `@README.md`:
- Around line 80-86: The fenced code block in the README.md "Continue" section
is missing a language tag (MD040); update the block under the "Continue" heading
by adding a language specifier (e.g., use "text") to the three-backtick fence so
it becomes ```text and avoid the lint failure.
🧹 Nitpick comments (2)
tests/continue/test-prompts.sh (2)

28-31: Frontmatter opening check doesn't verify first line specifically.

The current logic prints lines 1-4 and checks if any contains ^---$. This would pass if --- appears on line 2, 3, or 4 instead of line 1. Consider checking line 1 explicitly:

♻️ Suggested fix
-  if ! awk 'NR==1{print} NR==2{print} NR==3{print} NR==4{print}' "$path" | grep -q '^---$'; then
+  if ! head -n 1 "$path" | grep -q '^---$'; then
     echo "Prompt frontmatter must start with ---: $path"
     exit 1
   fi

33-46: Field checks match anywhere in file, not just frontmatter.

The grep patterns check the entire file, so a field appearing in the body content would also satisfy the check. Given the simple structure of these prompt files, this is unlikely to cause issues, but for stricter validation you could limit searches to the frontmatter block (between the two --- lines).

Comment on lines +80 to +86
### Continue

Tell Continue:

```
Fetch and follow instructions from https://raw.githubusercontent.com/obra/superpowers/refs/heads/main/.continue/INSTALL.md
```
Copy link

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

Add a language to the fenced code block.

The new Continue section includes a fenced block without a language tag (MD040). Add a language specifier to avoid lint failures.

Proposed fix
-```
+```text
 Fetch and follow instructions from https://raw.githubusercontent.com/obra/superpowers/refs/heads/main/.continue/INSTALL.md
</details>

<!-- suggestion_start -->

<details>
<summary>📝 Committable suggestion</summary>

> ‼️ **IMPORTANT**
> Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

```suggestion
### Continue

Tell Continue:

🧰 Tools
🪛 markdownlint-cli2 (0.18.1)

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

(MD040, fenced-code-language)

🤖 Prompt for AI Agents
In `@README.md` around lines 80 - 86, The fenced code block in the README.md
"Continue" section is missing a language tag (MD040); update the block under the
"Continue" heading by adding a language specifier (e.g., use "text") to the
three-backtick fence so it becomes ```text and avoid the lint failure.

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