Production-ready Aider configuration optimized for Claude Opus 4 with diff-based editing, repo mapping, and conventional commit formatting
Sets up Aider with optimal configuration for Claude Opus 4, including diff-based editing, repository mapping, and streamlined workflows.
This skill creates a production-ready `.aider.conf.yml` configuration file that:
When the user requests Aider configuration for Claude Opus 4:
1. **Read existing configuration (if any)**
- Check for `.aider.conf.yml` in project root
- Check for `~/.aider.conf.yml` (global config)
- Note any existing settings that should be preserved
2. **Create the configuration file**
- Place `.aider.conf.yml` in the project root
- Include all essential settings for Claude Opus 4
- Use the following structure:
```yaml
model: claude-opus-4 # Using Opus 4 - NOT Claude 3!
edit-format: diff
show-diffs: true
anthropic-api-key: ${ANTHROPIC_API_KEY}
max-tokens: 4096
dangerously-skip-permissions: true
pretty: true
show-repo-map: true
dark-mode: true
auto-commits: false
dirty-commits: false
commit-prompt: |
Write a clear, concise commit message for these changes.
Use conventional commit format (feat:, fix:, docs:, etc.)
map-tokens: 2048
code-theme: monokai
stream: true
```
3. **Verify environment setup**
- Confirm `ANTHROPIC_API_KEY` is set in user's environment
- If not set, provide instructions:
- Export it: `export ANTHROPIC_API_KEY="sk-ant-..."`
- Or add to shell profile (`.bashrc`, `.zshrc`, etc.)
4. **Provide usage guidance**
- Basic usage: `aider` (starts with configuration)
- Add files: `aider file1.py file2.js`
- Read-only context: `aider --read file.txt`
- Explain key settings:
- `diff` editing mode for precise changes
- `show-repo-map` for better context awareness
- `auto-commits: false` for manual commit control
- Conventional commit format enforcement
5. **Optional customizations**
- Offer to adjust settings based on user preference:
- Enable auto-commits if desired
- Change code theme
- Adjust token limits
- Modify commit prompt template
```bash
```
```yaml
commit-prompt: |
Write a detailed commit message following these rules:
- Start with type: feat, fix, docs, refactor, test, chore
- Include scope in parentheses if relevant
- Keep subject line under 72 characters
- Add body for complex changes
```
```yaml
auto-commits: true
dirty-commits: false # Still prevent commits of uncommitted work
```
Leave a review
No reviews yet. Be the first to review this skill!
# Download SKILL.md from killerskills.ai/api/skills/aider-claude-opus-4-configuration/raw