Aider Pro Configuration

A professional Aider configuration that includes intelligent commit message generation, multi-model support, and project-specific conventions.

What This Skill Does

This skill configures Aider with:

Configuration Steps

When setting up this Aider configuration:

1. **Create the `.aider.conf.yml` file** in your project root or home directory with the following structure:

2. **Model Selection**

- Primary model: `openrouter/anthropic/claude-opus-4.5` with `diff-fenced` edit format

- Alternative models available (commented out):

- OpenAI GPT-5.2

- Anthropic Claude Sonnet 4.5

- Google Gemini variants

- OpenAI O3 with reasoning

3. **Commit Message Rules**

- For `dotfiles` project files in `emacs/extras` or `emacs/extras/doc`:

- Format: `<filename-without-extension>: <lowercase description>`

- Example: `files-extras: refactor file handling functions`

- For `tlon` project files:

- Extract the middle part between `tlon-` and `.el`

- Format: `<extracted-name>: <description>`

- Example: For `tlon-tts.el` use `tts: add speech synthesis support`

- For other projects: Use standard commit conventions

- Maximum length: 70 characters

4. **Additional Settings**

- Enable auto-linting: `auto-lint: true`

- Read global conventions from: `~/Dropbox/dotfiles/aider/global_conventions.md`

- Disable co-author attribution: `attribute-co-authored-by: false`

- Disable committer attribution: `attribute-committer: false`

5. **File Content**

```yaml

models (uncomment as appropriate)

see https://aider.chat/docs/leaderboards/

model: openai/gpt-5.2

edit-format: diff-fenced

model: openrouter/anthropic/claude-opus-4.5

edit-format: diff-fenced

model: anthropic/claude-sonnet-4-5-20250929

edit-format: diff-fenced

model: gemini/gemini-2.5-flash-preview-05-20

model: gemini

edit-format: diff-fenced

weak-model: flash

thinking-tokens: 32k

check-model-accepts-settings: false

model: o3

reasoning-effort: high

other settings

commit-prompt: |

Generate a concise commit message following these rules:

- If the current project is `dotfiles` and the file(s) being committed are in `emacs/extras` or `emacs/extras/doc` (relative to that project), proceed as follows: (1) Begin with the name of the file being modified, sans its extension. For example, if the file is `emacs/extras/files-extras.el`, use `files-extras`. (2) Continue with ": " followed by a brief description of the change. The word after the colon should be in lowercase. For example, if you are refactoring a function in `emacs/extras/files-extras.el`, your commit message should look like this: `files-extras: <succinct description of the refactoring>`.

- If the current project is `tlon` and the file(s) being committed are in that directory or in the `doc` subdirectory, proceed as follows: Begin with the name of the file being modified, but instead of using the full file, only use the part between `tlon-` and `.el`. For example, if the file is `tlon-tts.el`, use `tts`. For documentation files, use what you would have used if you were writing a commit for the Elisp file being documented. For example, if the file is `tlon-tts.org`, use `tts`.

- Otherwise, just use standard commit rules.

- In all cases, the commit should not be longer than 70 characters.

auto-lint: true

read:

- ~/Dropbox/dotfiles/aider/global_conventions.md

attribute-co-authored-by: false

attribute-committer: false

```

Usage Examples

**Basic usage:**

```bash

aider

```

**With specific files:**

```bash

aider src/main.py tests/test_main.py

```

**Switch models by uncommenting the desired model in the config file**

Important Notes