TEAM LEARNINGS & RULES
Teach GitRabbit your team's specific coding styles and customs.
Every team has distinct architectural patterns, naming styles, and code formatting rules. GitRabbit learns your style automatically by analyzing your commit history. Additionally, you can specify custom rules inside YAML configuration files to mandate conventions (e.g. 'Use custom logger instead of console.log').
Key_Capabilities
Style Adaptability
The agent learns which pull requests are merged vs rejected, automatically fine-tuning its recommendations.
YAML System Guidelines
Write explicit instructions for specific folders or the entire repository.
Automated Enforcement
No more spending review time reminding team members about PascalCase namespaces or import orders.
Setup_Sequence
Add Guidelines
Define rules in '.gitrabbit/rules.yml' or in the GitRabbit Settings dashboard.
Historical Scan
The agent parses past merge history to understand standard library conventions.
Enforcement
Every subsequent PR will flag deviation from the learned standards.
Code_Example
# Rules configuration
rules:
- name: "No Direct Console Logs"
pattern: "console\.(log|error|warn)"
message: "Use our custom logging module: import { logger } from '@/lib/logger'"
severity: warning
- name: "PascalCase Components"
paths: ["frontend/components/**"]
message: "Ensure all component filenames are strictly PascalCase."Pro_Tips
- ✦Keep rules simple. GitRabbit handles complex semantic requirements without regex if you write clear messages.
- ✦Add examples of good code directly in the rules file to train the review agent faster.
- ✦Custom instructions are applied team-wide and can be version-controlled in Git.