Conversation
added 5 commits
February 22, 2026 11:53
…ent, dispatching-parallel-agents
…ment, using-git-worktrees
…iving-review, verification
📝 WalkthroughWalkthroughThis PR adds a new Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related issues
Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
🧹 Nitpick comments (1)
.kiro/steering/sp-finishing-a-development-branch.md (1)
1-3: Consider adding adescriptionfield to the frontmatter for slash-command discoverability.Manual steering files are invoked with
#<filename>in chat and also appear as slash commands — type/in chat to see and select them. Without adescriptionfield, the entry in the/menu has no summary text, making it harder for teammates unfamiliar with the skill set to pick the right command.✨ Suggested frontmatter addition (example for this file)
--- inclusion: manual +description: Workflow for cleanly finishing a development branch before merge. ---Apply the equivalent description to each of the 14
sp-*.mdsteering files.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In @.kiro/steering/sp-finishing-a-development-branch.md around lines 1 - 3, Add a description field to the frontmatter of this manual steering file so the slash-command menu shows a summary; specifically, update the YAML frontmatter in .kiro/steering/sp-finishing-a-development-branch.md (and apply the same change to all sp-*.md steering files) by adding a top-level description: "Concise one-line summary of what this steering command does" (replace with an appropriate summary for each file) so the `/` menu displays discoverable text.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In @.kiro/README.md:
- Around line 7-10: Update the Quick Start commands to include the missing "sp-"
prefix so they match the actual steering filenames; replace
`/using-superpowers`, `/brainstorming`, `/writing-plans`, and `/executing-plans`
with `/sp-using-superpowers`, `/sp-brainstorming`, `/sp-writing-plans`, and
`/sp-executing-plans` in the README so Kiro's slash commands map to the `sp-...`
steering files.
- Around line 24-29: The README currently claims "All skills are prefixed with
`sp-`" but the subsequent skill list shows names without that prefix; update the
skill list or its surrounding copy so it matches the stated convention: either
change each listed item to include the `sp-` prefix (e.g., `sp-brainstorming`,
`sp-writing-plans`, `sp-executing-plans`, `sp-subagent-driven-development`,
`sp-test-driven-development`, `sp-systematic-debugging`,
`sp-requesting-code-review`, `sp-receiving-code-review`,
`sp-verification-before-completion`, `sp-using-git-worktrees`,
`sp-finishing-a-development-branch`, `sp-dispatching-parallel-agents`,
`sp-writing-skills`) or add a parenthetical/clarifying sentence after "All
skills are prefixed with `sp-`" indicating that the list below omits the `sp-`
prefix for brevity (and that actual command/file names include it); adjust the
line that currently reads "All skills are prefixed with `sp-` to avoid
conflicts:" and the listed items accordingly.
---
Nitpick comments:
In @.kiro/steering/sp-finishing-a-development-branch.md:
- Around line 1-3: Add a description field to the frontmatter of this manual
steering file so the slash-command menu shows a summary; specifically, update
the YAML frontmatter in .kiro/steering/sp-finishing-a-development-branch.md (and
apply the same change to all sp-*.md steering files) by adding a top-level
description: "Concise one-line summary of what this steering command does"
(replace with an appropriate summary for each file) so the `/` menu displays
discoverable text.
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In @.kiro/README.md:
- Around line 14-20: The fenced code block in .kiro/README.md is missing a
language specifier and triggers markdownlint MD040; update the opening fence for
the directory-tree block in README.md (the triple backticks before the tree) to
include a language tag such as plaintext (e.g., change ``` to ```plaintext) so
the block becomes a fenced code block with a language specifier.
---
Duplicate comments:
In @.kiro/README.md:
- Around line 7-10: Update the quick-start list entries to include the missing
"sp-" prefix so the displayed slash commands match the steering file names;
specifically change "/using-superpowers", "/brainstorming", "/writing-plans",
and "/executing-plans" to "/sp-using-superpowers", "/sp-brainstorming",
"/sp-writing-plans", and "/sp-executing-plans" in the README so Kiro-derived
commands align with the sp-*.md steering files.
Comment on lines
+14
to
+20
| ``` | ||
| .kiro/ | ||
| ├── README.md # This file | ||
| └── steering/ # Kiro steering commands | ||
| ├── README.md # Command reference | ||
| └── sp-*.md # Individual skill steerings | ||
| ``` |
There was a problem hiding this comment.
Add a language specifier to the fenced code block (MD040).
The directory-tree block is missing a language tag, which triggers a markdownlint warning.
📝 Proposed fix
-```
+```plaintext
.kiro/
├── README.md # This file
└── steering/ # Kiro steering commands
├── README.md # Command reference
└── sp-*.md # Individual skill steerings</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
🧰 Tools
🪛 markdownlint-cli2 (0.21.0)
[warning] 14-14: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In @.kiro/README.md around lines 14 - 20, The fenced code block in
.kiro/README.md is missing a language specifier and triggers markdownlint MD040;
update the opening fence for the directory-tree block in README.md (the triple
backticks before the tree) to include a language tag such as plaintext (e.g.,
change ``` to ```plaintext) so the block becomes a fenced code block with a
language specifier.
obra
added
enhancement
4 tasks
Owner
|
Hi. Thanks so much for contributing this. #618 is closer to how we'd probably go about a Kiro integration. All those steering files are kind of a no-go |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Add Kiro steering files for all Superpowers skills to enable AI-assisted development workflow in Kiro IDE.
Changes
.kiro/steering/directory with 14 skill steeringsskills/<name>/SKILL.mdFiles Added
sp-*.mdsteering files (brainstorming, executing-plans, etc.).kiro/steering/README.md(command reference).kiro/README.md(root configuration)All steering files use
inclusion: manualfrontmatter and follow the kiro steering pattern.