test(cli): extract Kilo-specific instruction tests to own file#10027
Merged
Conversation
Move KILO_CONFIG_DIR profile fallback tests out of the shared upstream instruction.test.ts into packages/opencode/test/kilocode/instruction.test.ts to reduce future merge conflicts with opencode.
Contributor
Author
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Files Reviewed (2 files)
Reviewed by gpt-5.5-20260423 · 127,545 tokens |
chrarnoldus
approved these changes
May 7, 2026
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
Move the
KILO_CONFIG_DIRprofile fallback tests out of the shared upstreampackages/opencode/test/session/instruction.test.tsinto a Kilo-owned file atpackages/opencode/test/kilocode/instruction.test.ts. This reduces future merge conflicts with opencode by isolating Kilo-specific test logic inkilocode/directories where annotation markers aren't required.