git-ai-project/git-ai

Request to add support for **Kimi Code**

Open

#639 opened on Mar 5, 2026

View on GitHub
 (0 comments) (1 reaction) (0 assignees)Rust (231 forks)auto 404
agent-supportgood first issue

Repository metrics

Stars
 (2,272 stars)
PR merge metrics
 (PR metrics pending)

Description

Summary

Request to add support for Kimi Code (Moonshot AI's coding assistant) to enable accurate tracking and statistics of AI-generated code contributions within git repositories.

Background & Motivation

Kimi Code (月之暗面) has become one of the most widely used AI coding assistants, particularly in the Chinese developer community and increasingly globally. Currently, git-ai does not recognize Kimi Code's attribution markers, leading to:

  1. Underreported AI contribution metrics - Teams using Kimi Code cannot get accurate visibility into AI-assisted development
  2. Incomplete analytics - Mixed AI tool environments (GitHub Copilot + Kimi Code + others) produce skewed statistics
  3. Compliance gaps - Organizations requiring AI-generated code auditing lack visibility into Kimi contributions

Proposed Solution

Add detection patterns for Kimi Code's code attribution signatures. Based on typical usage patterns, Kimi Code generates markers such as:

# Generated by Kimi Code
# Created with Kimi (Moonshot AI)
# AI-generated by Kimi Code - Moonshot AI

Contributor guide

Research direction
Identify the current detection patterns for other AI tools (e.g., GitHub Copilot) in the codebase and add similar patterns for Kimi Code's attribution markers such as "Generated by Kimi Code" or "Created with Kimi (Moonshot AI)".
Tech stack
rust
Domain
clideveloper experience
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitRust
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75