feat: add Kilo Code support

[alacasse]

Closes #477

Added support for Kilo Code.

Summary

• Added Kilo Code as a supported platform in README and install scripts
• Added Kilo-specific skill and command files
• Added install/uninstall logic including plugin registration
• Extended tests for install flow, command detection, and registration
• Updated metadata for Kilo integration

[iwconfig]

This PR currently has 121 commits, which makes it vastly overscoped relative to its stated purpose. It looks like your branch accidentally included a lot of upstream history from v4. Additionally, the default branch is now v5. Your branch is stale.

Since all of your actual work is contained in a single commit (090aacb), the easiest way to fix this branch without opening a new PR is to reset it to v5 and cherry-pick your specific commit.

To do this, run the following commands (which use upstream to fetch directly from the main repository):

1. Add the main repository as upstream (if you haven't already):

git remote add upstream https://github.com/safishamsi/graphify.git

2. Fetch the latest branches from upstream:

git fetch upstream

3. Checkout your branch:

git checkout feat/kilo-support

4. Reset your branch to match the latest v5:
(This will safely wipe the 120+ extraneous commits from your branch history and align it with our new base)

git reset --hard upstream/v5

5. Cherry-pick your work onto the clean branch:

git cherry-pick 090aacba28ef80fbc4895a79013144aafd9328f1

6. Resolve conflicts (Only if the cherry-pick pauses):
Because you originally wrote this against v4, Git might pause if the code has changed in v5. If it does, resolve the conflicts in your editor, then run:

git add . # or whichever files had conflicts
git cherry-pick --continue

7. Force push to update THIS existing PR:

git push --force-with-lease origin feat/kilo-support

[Qodo-Free-For-OSS]

Hi, If a project has .kilo/kilo.jsonc, graphify kilo install will read it (after stripping comments) and then overwrite it using json.dumps, permanently deleting user comments and JSONC formatting.

Severity: action required | Category: correctness

How to fix: Avoid rewriting JSONC files

Agent prompt to fix - you can give this to your LLM of choice:

Issue description

When .kilo/kilo.jsonc exists, install/uninstall rewrites it as plain JSON via json.dumps(...), deleting comments and original formatting.

Issue Context

This is user-data loss. The code intentionally supports .jsonc (commented config), so it must not destroy comments.

Fix Focus Areas

• graphify/main.py[783-813]
  • Change the write strategy when config_file.suffix == '.jsonc'.
  • Options (pick one):
    • Prefer writing/maintaining .kilo/kilo.json for automated edits and leave .jsonc untouched.
    • Or implement a non-destructive JSONC edit approach (preserve original raw text and only inject the plugin entry without removing comments).
• graphify/main.py[816-836]
  • Apply the same non-destructive approach to uninstall (do not rewrite .jsonc as JSON).

---

Found by Qodo code review

[metheofanis]

Is there any progress?

[alacasse]

Is there any progress?

This branch now merges into V8, it should be possible to merge.
The default branch keeps changing, it's a moving target.

[iwconfig]

This branch now merges into V8, it should be possible to merge.

unfortunately you've included the upstream history again. As you can see this PR contains 86 commits, many of which do not belong to this PR.

And also, the PR is stale again. It points to v7, not v8. You must rebase your branch, or cherry-pick the commits like i explained earlier. Do not merge upstream changes. It clutters the PR diff.

The default branch keeps changing, it's a moving target.

Yeah, I must say it's a weird way of doing git for a fast-moving AI-driven project like this. For a mature, slow-moving project it's fine i think.

[alacasse]

This branch now merges into V8, it should be possible to merge.

unfortunately you've included the upstream history again. As you can see this PR contains 86 commits, many of which do not belong to this PR.

And also, the PR is stale again. It points to v7, not v8. You must rebase your branch, or cherry-pick the commits like i explained earlier. Do not merge upstream changes. It clutters the PR diff.

The default branch keeps changing, it's a moving target.

Yeah, I must say it's a weird way of doing git for a fast-moving AI-driven project like this. For a mature, slow-moving project it's fine i think.

Thank you.
I just fixed it all, it's for now without conflict. I hope it will be merged soon.

[alacasse]

Please merge this, each time there is a change in the project, the version changes and we have a conflict.
Or better, please change the versioning workflow or this PR will still be here in one year and I'd have spent 100 times how long it did take to write the code.

[safishamsi]

Merged 🎉 Thanks for the patience @alacasse - I know the rebase saga was painful, and you cleaned it up properly: 2 commits, rebased onto latest v8, no clutter.

Also verified the JSONC fix resolves the data-loss flag - existing .kilo/kilo.jsonc is read but never rewritten (plugin registration goes to kilo.json), so user comments are preserved. Ran the full suite (1525 passed) plus an install/uninstall smoke test before merging.

Point taken on the versioning friction - the frequent version bumps on the default branch do make long-lived PRs hard to keep current. Appreciate you sticking with it.

[alacasse]

Thank you @safishamsi! I'm glad this is merged and that people are going to be able to use it!

That said I was looking at the main.py installer and I think it's doing a lot.

I'd like to help out to split it and make it more maintainable. Would you find this helpful? I'd work on it in multiple passes as to not introduce too many changes at once. I'd provide a plan before working on it.

Cheers!

[safishamsi]

Go ahead please, happy to merge!

…

On Mon, 1 Jun 2026 at 17:21, alacasse ***@***.***> wrote: *alacasse* left a comment (Graphify-Labs/graphify#512) <#512 (comment)> Thank you @safishamsi <https://github.com/safishamsi>! I'm glad this is merged and that people are going to be able to use it! That said I was looking at the *main*.py installer and I think it's doing a lot. I'd like to help out to split it and make it more maintainable. Would you find this helpful? I'd work on it in multiple passes as to not introduce too many changes at once. I'd provide a plan before working on it. Cheers! — Reply to this email directly, view it on GitHub <#512>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BTSTP66NXHGJOBA7L5VJUYL45WUSFAVCNFSM6AAAAACYC25MZSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DKOJUGQ3DAMJYHA> . You are receiving this because you were mentioned.Message ID: ***@***.***>