kimchi:research

Investigate codebases to identify patterns, conventions, and anti-patterns.

8|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/Tromml/kimchi --skill kimchi-research
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kimchi:research
Source: https://github.com/Tromml/kimchi/tree/main/plugins/kimchi/skills/research
Command: npx skills add https://github.com/Tromml/kimchi --skill kimchi-research

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers understand existing code patterns, frameworks, and potential anti-patterns within a project before planning new features, ensuring consistency and efficiency.

Core Features & Use Cases

  • Codebase Pattern Detection: Identifies and documents recurring code structures, class/method definitions, and configuration blocks.
  • Framework Best Practice Research: Provides guidance on framework conventions when existing patterns are scarce.
  • Anti-Pattern Identification: Highlights code that violates conventions or introduces potential issues.
  • Use Case: Before adding a new authentication flow, a developer uses this Skill to find existing examples of user session management and token handling within the codebase, guiding the implementation.

Quick Start

Investigate the codebase for patterns related to user authentication.

Frequently Asked Questions about kimchi:research

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I investigate an existing codebase for patterns and conventions?

Investigate a codebase for patterns by using semantic search landmarks like `find:` to reference code elements, documenting recurring structures and framework conventions in a `RESEARCH.md` file.

What is codebase pattern detection and when do I need it?

Codebase pattern detection identifies recurring code structures, class definitions, and configuration blocks. You need it before planning new features to ensure implementation consistency and understand existing framework conventions.

Do I need specific context files to analyze code for anti-patterns?

Yes, analyzing code for anti-patterns requires `CONTEXT.md` and `REQUIREMENTS.md` files to be present from prior stages, ensuring the investigation aligns with existing project parameters and feature goals.

How do I identify framework conventions when existing code patterns are scarce?

Identify framework conventions during codebase research by analyzing available code structures; when patterns are scarce, the investigation provides guidance on framework best practices to guide new feature implementation.

What's the best way to document code research findings for feature planning?

Document code research findings by writing identified patterns, framework conventions, and anti-patterns directly into a `RESEARCH.md` file, creating a reference guide for subsequent feature implementation and planning.

Why does code research fail to find existing token handling patterns?

Code research fails to find existing token handling patterns when the required `CONTEXT.md` and `REQUIREMENTS.md` files are missing from prior stages, preventing accurate semantic search and pattern identification.