feat: add Kiro CLI/IDE platform support#364
Conversation
- Add kiro to install.sh platforms_table (per-skill symlinks to ~/.kiro/skills/) - Generate ~/.kiro/agents/understand.json on install for full pipeline support - Clean up agent JSON on uninstall - Add .kiro-plugin/plugin.json for IDE auto-discovery - Update README with Kiro in platform table, one-line install list, and dedicated section
Verification ReportAll tests were performed on macOS with Kiro CLI v1.x after running 1. Agent DiscoveryWhy: Confirms that Kiro CLI recognizes the generated Result: ✅ PASS 2. Agent Schema ValidationWhy: Ensures the generated JSON conforms to Kiro's agent configuration schema. Invalid JSON or missing required fields would cause a runtime error when attempting to use the agent. Result: ✅ PASS 3. Skill Symlink AccessibilityWhy: Verifies that the per-skill symlinks point to real files with valid YAML frontmatter. Kiro loads skills by scanning Result: ✅ PASS — All 8 skill symlinks resolve correctly, and 4. Prompt File Accessibility (45 KB)Why: The agent JSON uses Result: ✅ PASS — File exists at 5. Resources (Agent MDs) AccessibilityWhy: The agent JSON declares 7 agent definition files as Result: ✅ PASS — All 7 files accessible:
6. Core Package BuildWhy: SKILL.md's Phase 0 checks for Result: ✅ PASS — 7. End-to-End: Phase 0 (Pre-flight) ExecutionWhy: The ultimate integration test — runs the actual agent via Command: kiro-cli chat --agent understand --no-interactive --trust-all-tools \
"Run /understand on this project. Only do Phase 0 (pre-flight) and report what you find."Result: ✅ PASS — The agent executed Phase 0 flawlessly:
The agent correctly:
8. Uninstall CleanupWhy: Ensures Result: ✅ PASS SummaryAll 8 verification steps passed. The Kiro platform integration works end-to-end — from installation through agent discovery to actual pipeline execution. |
|
hi , any update for this PR ? |
|
@codex review this |
| "prompt": "file://$plugin_root/skills/understand/SKILL.md", | ||
| "tools": ["read", "write", "shell", "grep", "glob", "code", "subagent"], | ||
| "resources": [ | ||
| "file://$plugin_root/agents/project-scanner.md", |
There was a problem hiding this comment.
Hi, I would recommend do not hard code the agents, instead use loop of the repo dir.
There was a problem hiding this comment.
Use install.sh only is fine. If available, can you also consider adding install.ps1 for Windows user~
Lum1104
left a comment
There was a problem hiding this comment.
Thanks for the helping, I would appreciate it if you can help address the comment~ Feel free to leave a message if any help is needed~
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: ede10b9f12
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| ### Kiro CLI / IDE | ||
|
|
||
| ```bash | ||
| curl -fsSL https://raw.githubusercontent.com/Lum1104/Understand-Anything/main/install.sh | bash -s kiro |
There was a problem hiding this comment.
Point Kiro installs at the canonical repo
This new Kiro-specific command downloads install.sh from Lum1104/Understand-Anything, while the rest of this README and the installer default to Egonex-AI/Understand-Anything. For users following this exact snippet, Kiro support depends on a different fork having the new kiro platform entry; if it lags, the script exits with Unknown platform: kiro before it ever clones the canonical repo. Point this at the same Egonex URL used above.
Useful? React with 👍 / 👎.
|
|
||
| After installation: | ||
| - **Kiro CLI**: `kiro-cli chat --agent understand "Analyze this project"` | ||
| - **Kiro IDE**: Open the cloned repo — auto-discovered via `.kiro-plugin/plugin.json` |
There was a problem hiding this comment.
Do not claim Kiro auto-discovers .kiro-plugin
In the “open the cloned repo” path, nothing places these skills under Kiro's documented workspace scope (.kiro/skills/) or imports a specific skill folder/SKILL.md; the only new artifact is .kiro-plugin/plugin.json, which Kiro's skills/powers docs do not list as a discovery location. As a result, Kiro IDE users following this instruction will not see /understand until they run the installer or manually import/copy the skill folders.
Useful? React with 👍 / 👎.
Add Kiro CLI / IDE Platform Support
Summary
Adds Kiro (AWS AI IDE & CLI) as a supported platform for Understand-Anything.
Changes
install.shkiro|$HOME/.kiro/skills|per-skilltoplatforms_table~/.kiro/agents/understand.json(orchestrator agent with SKILL.md as prompt + agent MDs as resources)cmd_uninstall()to remove the agent JSON.kiro-plugin/plugin.json(new).copilot-plugin/and.cursor-plugin/)README.mdkiroto supported platform valuesInstallation
curl -fsSL https://raw.githubusercontent.com/Lum1104/Understand-Anything/main/install.sh | bash -s kiroAfter installation:
kiro-cli chat --agent understand "Analyze this project".kiro-plugin/plugin.jsonHow it works
~/.kiro/skills/(per-skill style, same as Codex/Gemini)~/.kiro/agents/understand.jsonreferences SKILL.md as the system prompt and agent MDs as resources, enabling the full analysis pipeline.kiro-plugin/plugin.jsonpoints toskills/andagents/(same pattern as Copilot/Cursor)Testing
install.sh kiro— 8 skill symlinks + agent JSON createdinstall.sh --uninstall kiro— all artifacts removed.kiro-plugin/plugin.jsonvalid JSONImpact on existing platforms
None. All changes are additive:
platforms_table(existing entries unchanged).kiro-plugin/directory (other.*-plugin/directories unchanged)