feat: Add comprehensive Kilo Code AI assistant support#336
feat: Add comprehensive Kilo Code AI assistant support#336shahrukhkhan489 wants to merge 0 commit intogithub:mainfrom
Conversation
|
@localden Kindly review and merge the request |
|
Kilo code, roo code and cline are identical |
|
+1 for adding this as a supported platform. |
shahrukhkhan489
force-pushed
the
main
branch
from
bb81aff to
91a1502
Compare
localden
left a comment
localden
left a comment
There was a problem hiding this comment.
Overall, I think this is going in a good direction. I just have a few concerns with Kilo-specific code in the shell script.
|
|
||
| # Apply other substitutions | ||
| body=$(printf '%s\n' "$body" | sed "s/{ARGS}/$arg_format/g" | sed "s/__AGENT__/$agent/g" | rewrite_paths) | ||
| # Special handling for Kilo Code YAML format |
There was a problem hiding this comment.
Is Kilo Code the only one using YAML?
There was a problem hiding this comment.
Nope...Roo-Code and Cline use YAML as well
So once this works ....the same can be extended for the others as well
| body=$(printf '%s\n' "$body" | sed "s/{ARGS}/$arg_format/g" | sed "s/__AGENT__/$agent/g" | rewrite_paths) | ||
| # Special handling for Kilo Code YAML format | ||
| if [ "$ext" = "yaml" ]; then | ||
| # Process body for Kilo Code format |
There was a problem hiding this comment.
Same here - feels a bit odd that we're saying here that it's Kilo Code-targeted when YAML can be very generic. And if Kilo Code is using something that is "custom YAML," for example, we should make that explicit.
| processed_content=$(echo "$file_content" | sed "s|{SCRIPT}|${script_command}|g") | ||
| yaml_body=$(echo "$processed_content" | awk ' | ||
| BEGIN { in_body = 0 } | ||
| /^---$/ { |
src/specify_cli/__init__.py
Outdated
| steps_lines.append(" - Run qwen /plan to create implementation plans") | ||
| steps_lines.append(" - Run qwen /tasks to generate tasks") | ||
| steps_lines.append(" - See QWEN.md for all available commands") | ||
| elif selected_ai == "kilocode": |
There was a problem hiding this comment.
This is no longer applicable - you should rebase to latest version.
src/specify_cli/__init__.py
Outdated
| "claude": "Claude Code", | ||
| "gemini": "Gemini CLI", | ||
| "cursor": "Cursor", | ||
| "kilocode": "Kilo Code", |
There was a problem hiding this comment.
Any changes to __init__.py should be accompanied by a package version rev and update to the CHANGELOG.md
localden
added
enhancement
merge-candidate
|
i will rebase the code and resend the pull request for approval.....we can use markup instead of yaml using the kilo code workflow feature |
shahrukhkhan489
force-pushed
the
main
branch
from
f629674 to
5659c86
Compare
4 participants
🎯 Summary
This PR adds complete support for Kilo Code as a new AI assistant in the Spec Kit ecosystem. Kilo Code is treated as an IDE extension (similar to Cursor and GitHub Copilot) and includes full integration across all components.
Closes #282
✨ Features Added
🔧 Core Integration
.kilocodemodesfile generation for Kilo Code packages📚 Documentation Updates
🛠️ Technical Implementation
.kilocodemodesfile generation🔄 User Experience
Users can now initialize Spec Kit projects with Kilo Code support:
This generates:
.kilocodemodesfile with custom modes for Kilo Code🧪 Testing
📊 Impact
This PR expands Spec Kit's AI assistant support matrix to include:
🔗 Related Issues
✅ Checklist
This PR brings Kilo Code support to Spec Kit, enabling users to leverage Kilo Code's capabilities within the Spec-Driven Development workflow! 🚀
Addresses: #282