Skip to content

feat(init): add support for kilocode and antigravity agents#802

Open
Yosoyepa wants to merge 1 commit intortk-ai:developfrom
Yosoyepa:feat/add-new-agents
Open

feat(init): add support for kilocode and antigravity agents#802
Yosoyepa wants to merge 1 commit intortk-ai:developfrom
Yosoyepa:feat/add-new-agents

Conversation

@Yosoyepa
Copy link
Copy Markdown

Add support for generating rules for Kilo Code and Google Antigravity via rtk init.

Summary

  • Added CLI Flags: Extended AgentTarget to support --agent kilocode and --agent antigravity.
  • Injected Agent Rules: Created specific markdown instruction files matching the original token-loss guidelines for both assistants (.kilocode/rules/rtk-rules.md and .agent/rules/antigravity-rtk-rules.md).
  • Maintained Code Style: Kept the new init::run console outputs consistent and free of emojis to strictly follow the project's formatting conventions.

Test plan

  • cargo fmt --all && cargo clippy --all-targets && cargo test
  • Manual testing: rtk <command> output inspected (Successfully tested rtk gain, rtk git status locally to ensure the new settings inject and reduce token usage without issues).

@CLAassistant
Copy link
Copy Markdown

CLAassistant commented Mar 25, 2026

CLA assistant check
All committers have signed the CLA.

@pszymkowiak pszymkowiak added effort-small Quelques heures, 1 fichier enhancement New feature or request labels Mar 25, 2026
@pszymkowiak
Copy link
Copy Markdown
Collaborator

[w] wshm · Automated triage by AI

📊 Automated PR Analysis

Type feature
🟢 Risk low

Summary

Adds support for two new agent targets (Kilo Code and Google Antigravity) to the rtk init command. This includes new CLI flags, markdown rule files for each agent, and corresponding init mode functions that write rules to agent-specific directories.

Review Checklist

  • Tests present
  • Breaking change
  • Docs updated

Analyzed automatically by wshm · This is an automated analysis, not a human review.

@aeppling
Copy link
Copy Markdown
Contributor

Hey

We are cleaning up the codebase and improving the project structure for better onboarding. As part of this effort, PR #826 reorganizes src/ from a flat layout into subfolders.

No logic changes — only file moves and import path updates.

What you need to do

Rebase your branch on develop when receiving this comment:

git fetch origin && git rebase origin/develop

Git detects renames automatically. If you get import conflicts, update the paths:

use crate::git;        // now: use crate::cmds::git::git;
use crate::tracking;   // now: use crate::core::tracking;
use crate::config;     // now: use crate::core::config;
use crate::init;       // now: use crate::hooks::init;
use crate::gain;       // now: use crate::analytics::gain;

Need help rebasing? Tag @aeppling

@Yosoyepa Yosoyepa force-pushed the feat/add-new-agents branch from f16400e to f3f4993 Compare March 27, 2026 04:46
@Yosoyepa
Copy link
Copy Markdown
Author

Hi @aeppling, thanks for the heads up!

I've successfully fetched the latest develop branch, rebased my branch, and resolved all conflicts to align with the new src/hooks/ subfolder structure. The rebase has been force-pushed and the new structure is perfectly integrated!

Let me know if everything looks good on your end or if there's anything else needed. Thanks!

@Yosoyepa Yosoyepa force-pushed the feat/add-new-agents branch from f3f4993 to f72f7c5 Compare April 1, 2026 00:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

effort-small Quelques heures, 1 fichier enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants