[Feature] Custom File Paths, Rules, and Instructions

[LinceMathew]

Description

Add an option to pass custom file paths, rules, and instructions to git-lrc on each review. These instructions can be stored as markdown or JSON files in a .lrc/ directory within the repository.

Use Cases

1. Include Architecture/Design Documents

Send AGENTS.md or DESIGN.md files for each review to validate code changes against the design specifications.

Example:

Include: DESIGN.md
Purpose: Validate code changes against architecture guidelines

2. Define Custom Rule Sets

Create custom rules for different parts of the codebase with specific validation requirements.

Example:

{
  "rules": [
    {
      "path": "sample/**/*.py",
      "rule": "All new methods must validate required parameters for null values"
    },
    {
      "path": "src/api/**/*.js",
      "rule": "All API endpoints must include proper error handling and logging"
    }
  ]
}

3. Pass Custom LLM Instructions

Include custom prompts and instructions tailored to your project's coding standards and best practices.

Example:

• Enforce naming conventions: camelCase for variables, PascalCase for classes
• Check for proper error handling and logging
• Validate security best practices

Implementation Suggestions

Store configuration in .lrc/ directory with support for:

• config.json or config.md for custom instructions
• rules.json for rule definitions
• References to other documentation files (DESIGN.md, AGENTS.md, etc.)

These files would be automatically picked up by git-lrc during the review process.

[shrsv]

I recommend toml. Also a simple include.toml with references to various md files in repo good enough, I think.

[shrsv]

Another thing to consider in toml is references to skills or such thing as @lovestaco recommended. How to easily embed "pre-built" rulesets, etc

Also - I think before we standardize a solution, I recommend actually working through some real examples, thinking through it from first principles