Skip to content

Add Kiro IDE support to install.sh and install.ps1#511

Merged
dustinvannoy-db merged 2 commits into
databricks-solutions:mainfrom
antonyprasad-db:add-kiro-databricks-power
May 4, 2026
Merged

Add Kiro IDE support to install.sh and install.ps1#511
dustinvannoy-db merged 2 commits into
databricks-solutions:mainfrom
antonyprasad-db:add-kiro-databricks-power

Conversation

@antonyprasad-db
Copy link
Copy Markdown
Contributor

Summary

Adds kiro as a selectable tool target in the unified installer, mirroring the existing per-tool integration pattern (claude, cursor, copilot, codex, gemini, antigravity).

Changes

  • Help text / --tools list — adds kiro to the comma-separated options
  • Tool detection/Applications/Kiro.app or kiro command (Bash); %LOCALAPPDATA%\Programs\Kiro\Kiro.exe or kiro command (PowerShell)
  • Skill install path<base>/.kiro/skills/<skill>/SKILL.md (project) or ~/.kiro/skills/ (global)
  • MCP config<base>/.kiro/settings/mcp.json (project) or ~/.kiro/settings/mcp.json (global), reuses the existing write_mcp_json helper

Schema sources

Per Kiro IDE docs:

Test plan

  • bash install.sh --tools kiro --silent writes skills to .kiro/skills/ and MCP config to .kiro/settings/mcp.json
  • --help and --tools validation reflect the new option
  • Detection picks up Kiro.app on macOS and the kiro CLI on PATH
  • PowerShell equivalent verified on Windows

This pull request and its description were written by Isaac.

Adds 'kiro' as a selectable tool target in the unified installer,
mirroring the existing per-tool integration pattern (claude, cursor,
copilot, codex, gemini, antigravity).

Per Kiro IDE docs (kiro.dev/docs/skills, kiro.dev/docs/mcp/configuration):
- Skills install to .kiro/skills/<skill>/SKILL.md (project) or
  ~/.kiro/skills/ (global). Same SKILL.md schema as Claude/Cursor —
  no skill content changes required.
- MCP config writes to .kiro/settings/mcp.json (project) or
  ~/.kiro/settings/mcp.json (global). Same {"mcpServers": ...}
  schema, so the existing write_mcp_json helper is reused.

Detection looks for /Applications/Kiro.app or a 'kiro' command (Bash),
and %LOCALAPPDATA%\Programs\Kiro\Kiro.exe or 'kiro' command (PowerShell).

Co-authored-by: Isaac
@dustinvannoy-db dustinvannoy-db self-requested a review May 2, 2026 03:46
@dustinvannoy-db
Copy link
Copy Markdown
Collaborator

@antonyprasad-db this is looking good but it needs to merge in main. Please also check that when there is a full list of coding tools it includes windsurf, opencode, and kiro along with the others that have been in the repo a while. I think opencode may not be listed everywhere it should in main.

Copy link
Copy Markdown
Collaborator

@dustinvannoy-db dustinvannoy-db left a comment

Choose a reason for hiding this comment

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

Merge main and make sure list of tools is complete (see other note for explanation)

- Resolves merge with main which added Windsurf (databricks-solutions#478) and OpenCode (databricks-solutions#492).
- Combines all three new tools (windsurf, opencode, kiro) in a consistent
  order at every touch point: header comment, --tools help text, detection,
  checkbox UI, silent default, skill install path, MCP config, and final
  launch instructions.
- Adds Kiro launch instruction to the post-install steps (was missing in
  the original PR).
- Brings Windsurf and OpenCode into the header comment alongside the other
  tools (per reviewer note that opencode wasn't listed everywhere on main).
- Kiro skill install now supports both global (~/.kiro/skills) and project
  (.kiro/skills) scopes, mirroring windsurf/opencode.

Co-authored-by: Isaac
@antonyprasad-db
Copy link
Copy Markdown
Contributor Author

@dustinvannoy-db thanks for the review! Pushed an update that addresses both points:

1. Merged main in — branch is now MERGEABLE (no more conflicts).

2. Full coding-tools coverage:

  • Combined Windsurf, OpenCode, and Kiro into all installer touch points in a consistent order (header comment, --tools help text, detection vars/logic, checkbox UI, silent default, skill install path, MCP config write, and final launch instructions).
  • Added Kiro to the post-install launch instructions (was missing in the original PR).
  • Updated the header comment to explicitly list Windsurf, OpenCode, and Kiro alongside the others — this also closes the gap you flagged where OpenCode wasn't listed in main's header.
  • Kiro skill install now supports both global (~/.kiro/skills) and project (.kiro/skills) scopes, mirroring the windsurf/opencode pattern.

Ready for another look when you have a chance.

Copy link
Copy Markdown
Collaborator

@dustinvannoy-db dustinvannoy-db left a comment

Choose a reason for hiding this comment

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

LGTM

@dustinvannoy-db dustinvannoy-db merged commit 024d22a into databricks-solutions:main May 4, 2026
dustinvannoy-db added a commit that referenced this pull request May 7, 2026
Adds 'kiro' as a selectable tool target in the unified installer,
mirroring the existing per-tool integration pattern (claude, cursor,
copilot, codex, gemini, antigravity).

Per Kiro IDE docs (kiro.dev/docs/skills, kiro.dev/docs/mcp/configuration):
- Skills install to .kiro/skills/<skill>/SKILL.md (project) or
  ~/.kiro/skills/ (global). Same SKILL.md schema as Claude/Cursor —
  no skill content changes required.
- MCP config writes to .kiro/settings/mcp.json (project) or
  ~/.kiro/settings/mcp.json (global). Same {"mcpServers": ...}
  schema, so the existing write_mcp_json helper is reused.

Detection looks for /Applications/Kiro.app or a 'kiro' command (Bash),
and %LOCALAPPDATA%\Programs\Kiro\Kiro.exe or 'kiro' command (PowerShell).

Co-authored-by: antonyprasad-db <antonyprasad.thevaraj@databricks.com>
Co-authored-by: Antony Prasad Thevaraj <280810845+antonyprasad-db@users.noreply.github.com>
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.

2 participants