feat(init): add Kiro IDE support #648
Open
Conversation
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
- Add Kiro IDE to AI_TOOLS registry with skillsDir '.kiro' - Create kiro adapter generating .kiro/steering/opsx-*.md files - Use 'inclusion: always' frontmatter for Kiro steering files - Register kiro in CommandAdapterRegistry - Add legacy cleanup path pattern for Kiro - Add unit tests for kiro adapter - Update docs/supported-tools.md with Kiro configuration Generated with Kiro IDE using Claude Opus 4.5
Contributor
📝 WalkthroughWalkthroughAdds Kiro IDE support: new Changes
Sequence Diagram(s)sequenceDiagram
participant CLI as CLI
participant Registry as CommandAdapterRegistry
participant Adapter as kiroAdapter
participant FS as Filesystem
CLI->>Registry: request adapter for tool "kiro"
Registry->>Adapter: select kiroAdapter
CLI->>Adapter: provide CommandContent (id, name, body, description)
Adapter->>Adapter: formatFile() -> markdown with YAML frontmatter
Adapter->>FS: write `.kiro/steering/opsx-<id>.md`
FS-->>CLI: file created
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 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 |
Review CompleteYour review story is ready! Comment !reviewfast on this PR to re-generate the story. |
Greptile OverviewGreptile SummaryAdded Kiro IDE support to OpenSpec following the established adapter pattern. Key Changes:
Notes:
Confidence Score: 4/5
Important Files Changed
Sequence DiagramsequenceDiagram
participant User
participant CLI as OpenSpec CLI
participant Registry as CommandAdapterRegistry
participant KiroAdapter as kiroAdapter
participant FS as File System
User->>CLI: openspec init --tools kiro
CLI->>Registry: Load adapters
Registry->>KiroAdapter: register(kiroAdapter)
Note over KiroAdapter: toolId: 'kiro'<br/>skillsDir: '.kiro'
loop For each command (explore, new, apply, etc.)
CLI->>KiroAdapter: getFilePath(commandId)
KiroAdapter-->>CLI: .kiro/steering/opsx-{commandId}.md
CLI->>KiroAdapter: formatFile(content)
Note over KiroAdapter: Format with frontmatter:<br/>inclusion: always
KiroAdapter-->>CLI: Formatted markdown with YAML
CLI->>FS: Write file to .kiro/steering/
FS-->>CLI: Success
end
CLI->>FS: Write skills to .kiro/skills/
FS-->>CLI: Complete
CLI-->>User: Kiro IDE configured
|
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In `@src/core/command-generation/adapters/kiro.ts`:
- Around line 13-15: The file-level comment that describes the Kiro steering
file frontmatter incorrectly lists name and description as YAML frontmatter
fields; update that comment so it only documents the supported frontmatter keys
(inclusion and fileMatchPattern) and note that name and description are emitted
into the markdown body (not the YAML frontmatter) — edit the top comment block
in src/core/command-generation/adapters/kiro.ts to remove references to
name/description from the frontmatter section and clarify that only inclusion
and fileMatchPattern belong in YAML while name/description are body content
(referencing the existing emitted keys "inclusion" and "fileMatchPattern" in the
code).
Contributor
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In `@openspec/changes/add-kiro-support/tasks.md`:
- Around line 8-9: The spec files incorrectly document a single fixed steering
file name; update cli-init/spec.md and kiro-integration/spec.md to state that
Kiro produces per-command steering files using the pattern
`.kiro/steering/opsx-<commandId>.md` to match the adapter implementation; mirror
the logic in src/core/command-generation/adapters/kiro.ts by referencing its
getFilePath() behavior and replace any occurrences of
`.kiro/steering/openspec.md` with the per-command pattern and an explanatory
note that `<commandId>` corresponds to the command's id.
🧹 Nitpick comments (2)
openspec/changes/add-kiro-support/specs/cli-init/spec.md (1)
31-49: Clarify where users can add custom content.The file structure examples show all content wrapped within the OpenSpec managed markers (
<!-- OPENSPEC:START -->/<!-- OPENSPEC:END -->). However, the update requirements inkiro-integration/spec.md(line 103) specify preserving "user content outside the markers."Consider adding an example or note showing where users can safely add custom content that won't be overwritten during
openspec update.Also applies to: 55-73
openspec/changes/add-kiro-support/specs/kiro-integration/spec.md (1)
54-55: Consider explaining Kiro's file reference syntax.The spec mentions using Kiro's
#[[file:]]syntax but doesn't explain its purpose or behavior. For readers unfamiliar with Kiro IDE, a brief note explaining that this syntax allows Kiro to include the referenced file's content in the AI context would improve clarity.Also applies to: 60-61
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Generated with Kiro IDE using Claude Opus 4.5
Summary by CodeRabbit
New Features
Documentation
Behavior
Tests