Aider Configuration Expert

This skill configures Aider (AI pair programming tool) with professional settings optimized for Claude Sonnet 4.5, structured commit messages, and streamlined development workflows.

What This Skill Does

Sets up Aider with:

Instructions

When the user requests Aider configuration or provides an `.aider.conf.yaml` file:

1. **Analyze Requirements**

- Check if user has specific model preferences

- Identify any custom commit message conventions

- Note any organizational requirements (e.g., ticket prefixes)

2. **Generate Configuration File**

Create `.aider.conf.yaml` with these settings:

```yaml

chat-language: english

analytics: false

code-theme: gruvbox-dark

attribute-author: false

attribute-committer: false

analytics-disable: true

auto-commits: false

model: openai/claude-sonnet-4.5

weak-model: openai/gpt-4.1

show-model-warnings: false

edit-format: diff-fenced

commit-prompt: |

You are an expert software engineer that generates concise,

one-line Git commit messages based on the provided diffs.

Review the provided context and diffs which are about to be committed to a git repo.

Review the diffs carefully.

Generate a one-line commit message for those changes.

The commit message should be structured as follows: <type>(<scope>): <description>

Use these for <type>: fix, feat, build, ci, chore, refactor

Ensure the commit message:

- Starts with the appropriate prefix.

- Is in the imperative mood (e.g., "add feature" not "added feature" or "adding feature").

- Does not exceed 72 characters.

Scope is optional, use branch name if branch starts with `DNA-` or `ID-` prefix (i.e. "feat(DNA-5444): change map style via dialog"

Reply only with the one-line commit message, without any additional text, explanations, or line breaks.

```

3. **Customize for Context**

- Replace `DNA-` or `ID-` prefixes with organization-specific ticket patterns

- Adjust model choices if user has API access constraints

- Modify commit types if project uses different conventions

- Change theme if user prefers different syntax highlighting

4. **Explain Key Settings**

- **Model choice**: Claude Sonnet 4.5 for quality, GPT-4.1 as efficient fallback

- **Diff-fenced format**: Clean, reviewable diffs

- **Auto-commits disabled**: Gives developer control over when to commit

- **Commit prompt**: Enforces conventional commits with ticket tracking

- **Privacy**: All analytics disabled

5. **Provide Usage Guidance**

- Place `.aider.conf.yaml` in project root or `~/.aider/` for global config

- Run `aider` in terminal to start with these settings

- Use `/commit` command to generate structured commit messages

- Customize `weak-model` based on budget/speed requirements

Examples

Basic Setup

User: "Set up Aider for my project"

→ Generate `.aider.conf.yaml` with standard settings

Custom Ticket Prefix

User: "We use JIRA-1234 format for tickets"

→ Modify scope detection: `if branch starts with 'JIRA-' prefix`

Different Models

User: "I only have access to OpenAI models"

→ Change to `model: gpt-4-turbo` and `weak-model: gpt-3.5-turbo`

Team Standards

User: "Our team uses Angular commit convention"

→ Adjust commit types to include: `docs, style, test, perf`

Constraints