-
-
Notifications
You must be signed in to change notification settings - Fork 3k
feat: Add Continue integration #302
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
📝 WalkthroughWalkthroughAdds 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
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches
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. Comment |
There was a problem hiding this 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
greppatterns 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).
| ### Continue | ||
|
|
||
| Tell Continue: | ||
|
|
||
| ``` | ||
| Fetch and follow instructions from https://raw.githubusercontent.com/obra/superpowers/refs/heads/main/.continue/INSTALL.md | ||
| ``` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
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:
.continue/INSTALL.md).continue/prompts/*.prompt) that show up in Continue’s/menuHow Has This Been Tested?
bash tests/continue/test-prompts.shto validate all Continue.promptfiles exist and contain required frontmatter (name,description,invokable: true):by quotingnamevalues (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
Checklist
https://modelcontextprotocol.ioAdditional context
.promptextension andsuperpowers-filename prefix:superpowers-bootstrap.promptsuperpowers-brainstorm.promptsuperpowers-write-plan.promptsuperpowers-execute-plan.prompt~/.continue/skills/superpowers -> ~/.continue/superpowers/skills.continue/prompts/*.promptinto~/.continue/prompts/Reload Config.tests/continue/test-prompts.sh) to prevent regressions in prompt frontmatter/paths.Summary by CodeRabbit
Documentation
New Prompts
Tests
Chores
✏️ Tip: You can customize this high-level summary in your review settings.