GitSniff LogoGitSniffDocs
Configuration

Custom Instructions

Provide custom review guidelines using instruction files in your repository.

GitSniff supports custom instruction files that let you define project-specific guidelines for AI review, chat, and auto-fix.

Instruction file formats

GitSniff reads instructions from your repository in this priority order:

For Code Review (action-driven)

Code Review uses only the OpenCode instruction format:

  1. .opencode/instructions.md — Primary instruction file for review behavior

OpenCode skills from .opencode/skill/*/SKILL.md are also auto-discovered and used during review.

For Chat and Auto-fix (context-driven)

Chat and Auto-fix support multiple instruction formats, checked in this order:

  1. .opencode/instructions.md
  2. .claude/instructions.md or CLAUDE.md
  3. .cursor/instructions.md
  4. .copilot/instructions.md
  5. AGENT.md

The first file found is used. Other files (CLAUDE.md, etc.) are loaded as additional context.

What to include

Your instruction file can contain:

  • Custom review preferences — Strictness level, focus areas, things to ignore
  • Coding standards — Language conventions, naming patterns, architecture rules
  • Project context — Technology stack, important dependencies, deployment requirements
  • Ignore patterns — Files or patterns to skip during review

Example instruction file

# Review Instructions

## Focus Areas
- Pay special attention to error handling
- Check for proper input validation on all API endpoints
- Ensure all database queries use parameterized statements

## Coding Standards
- Use TypeScript strict mode
- Prefer async/await over callbacks
- All public functions must have JSDoc comments

## Ignore
- Skip review of auto-generated files in /generated/
- Don't flag TODO comments in test files

Dashboard instructions

You can also set custom instructions through the dashboard without adding files to your repository:

  • Organization level: Dashboard > Settings > Custom Instructions
  • Repository level: Dashboard > Repository > Settings > Custom Instructions

Dashboard instructions are combined with file-based instructions. File-based instructions take priority when there are conflicts.