feat: add Kilo CLI (KiloCode) as fully supported platform

[Exc1D]

Summary

Adds Kilo CLI (KiloCode) as a first-class supported platform — MCP config, auto-detection, platform instructions, AND Kilo-native skill files.

Changes

code_review_graph/skills.py

1. MCP config: kilocode platform entry

Added kilocode to the PLATFORMS dict:

• config_path: .opencode/opencode.jsonc (Kilo stores config inside .opencode/ dir — the only structural difference from OpenCode)
• detect: checks for .opencode/opencode.jsonc existence
• format, key, needs_type: identical to OpenCode

2. Skill files: generate_kilo_skills()

New function that generates 4 skill files to .kilocode/skills/:

Skill file	Purpose
explore-codebase.md	Navigate codebase using graph tools
review-changes.md	Risk-scored code review workflow
debug-issue.md	Graph-powered systematic debugging
refactor-safely.md	Dependency-aware refactoring

Each skill mirrors the Claude Code .claude/skills/ versions — same body, same frontmatter, just in Kilo's skill directory.

code_review_graph/cli.py

• Added generate_kilo_skills to imports
• init now calls both generate_skills() and generate_kilo_skills()
• Print output distinguishes Claude Code vs Kilo skills

docs/USAGE.md

• Added Kilo CLI to the supported platforms table
• Fixed OpenCode's config path (was incorrectly listed as .opencode/config.json)

Platform comparison

What gets installed	Claude Code	OpenCode	Kilo CLI	Cursor	Windsurf
MCP server config	.mcp.json	.opencode.json	.opencode/opencode.jsonc	.cursor/mcp.json	~/.codeium/...
AGENTS.md (graph instructions)	✓	✓	✓ (inherits)	✓	✗
Platform skill files	.claude/skills/	✗	.kilocode/skills/	✗	✗

Testing

# Auto-detect all platforms including Kilo CLI
code-review-graph install

# Init Claude Code + Kilo CLI skill files
code-review-graph init

# Preview Kilo MCP config
code-review-graph install --platform kilocode --dry-run

Note

The README's diagram8_supported_platforms.png shows supported platforms visually and will need to be regenerated to include Kilo CLI. Left unchanged since it requires the maintainer's design tools.

[tirth8205]

Thanks for adding Kilo CLI support! The platform entry follows our patterns well. A few things to address:

1. No tests. Every other platform has tests in test_skills.py (see TestPlatformInstall). Please add tests for generate_kilo_skills() and the kilocode platform config.

2. JSONC parsing issue. The config path is .opencode/opencode.jsonc — JSONC allows comments, but our install_platform_configs reads with json.loads() which will crash on commented files. This would silently destroy the user's config (caught by the try/except, but the file gets overwritten). Consider using a JSONC-tolerant reader or documenting this limitation.

3. Kilo skills generated unconditionally. init calls generate_kilo_skills() regardless of whether Kilo is installed. This creates a .kilocode/ directory in every repo. Should this be gated behind detection or --platform kilocode?