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-ai-reviewer]

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