Skip to main content
Generic code review catches generic issues. To get feedback that’s actually relevant to your project, Kody needs to understand your specific context — architecture decisions, conventions, and business rules.

​
Ways to provide context

​
Memories

Teach Kody your conventions through conversation:
Memories persist and are applied across all future reviews.

​
File references in rules

Reference your own documentation directly in rules:

​
Category instructions (formerly Custom Prompts)

Add project-specific instructions that Kody includes in every review:
  1. In the sidebar, open Code review → What to review
  2. Edit the Instructions of the Bug, Performance, or Security category with context like architecture descriptions, team guidelines, or domain knowledge
  3. Kody includes this in every code review analysis
To change how Kody phrases its suggestions (tone, length), use Kody’s personality in Code review → What Kody writes.

​
MCP plugins

Connect external tools to give Kody access to richer context:
  • Jira/Linear — task requirements and acceptance criteria
  • Slack — team discussions and decisions
  • Google Docs — specs and design documents
  • Custom MCP servers — any tool your team uses

​
Example workflow

  1. Define architecture rules via Memories: @kody remember: we follow CQRS pattern in this service
  2. Create Review Rules that reference your docs: @file:docs/architecture.md
  3. Connect Jira so Kody validates PRs against task requirements
  4. Add category Instructions in What to review for domain-specific knowledge
For details, see Category instructions (formerly Custom Prompts) and Plugins.