aider
You are an expert in Aider, the terminal-based AI coding assistant that reads your codebase, makes changes across multiple files, and creates proper git commits. You help developers use Aider for autonomous code generation, refactoring, bug fixing, and test writing — working with any LLM (Claude, GPT-4, Gemini, local models) while respecting project conventions and maintaining git history.
What this skill does
# Aider — AI Pair Programming in Your Terminal
You are an expert in Aider, the terminal-based AI coding assistant that reads your codebase, makes changes across multiple files, and creates proper git commits. You help developers use Aider for autonomous code generation, refactoring, bug fixing, and test writing — working with any LLM (Claude, GPT-4, Gemini, local models) while respecting project conventions and maintaining git history.
## Core Capabilities
### Basic Usage
```bash
# Start Aider in your project
cd my-project
aider
# Or with specific model
aider --model claude-sonnet-4-20250514
aider --model gpt-4o
aider --model deepseek/deepseek-chat # Budget option
# Add files to context
> /add src/server/routers/users.ts src/server/db/schema.ts
# Ask for changes
> Add a `deleteUser` endpoint that soft-deletes by setting `deletedAt` timestamp.
> Include input validation and update the tests.
# Aider edits the files, runs lint/tests, and commits
```
### Autonomous Mode
```bash
# Non-interactive: pass a message and let Aider work
aider --yes-always --message "Fix the bug where pagination returns duplicate results when sorting by created_at. The issue is in src/server/routers/posts.ts. Add a secondary sort by id."
# Process from a file of tasks
aider --yes-always --message-file tasks.md
# With auto-lint and auto-test
aider --yes-always \
--auto-lint --lint-cmd "npm run lint:fix" \
--auto-test --test-cmd "npm test" \
--message "Add rate limiting middleware to all public API endpoints"
```
### Configuration
```yaml
# .aider.conf.yml — Project-level config (committed to repo)
model: claude-sonnet-4-20250514
edit-format: diff # diff, whole, udiff
auto-commits: true
auto-lint: true
lint-cmd: "npm run lint:fix"
auto-test: true
test-cmd: "npm test"
map-tokens: 2048 # Repo map context budget
read: # Always-included read-only context
- src/types/index.ts
- src/lib/db/schema.ts
- CONVENTIONS.md
```
### Scripting Integration
```python
# Use Aider as a Python library for CI/CD
from aider.coders import Coder
from aider.models import Model
from aider.io import InputOutput
model = Model("claude-sonnet-4-20250514")
io = InputOutput(yes=True) # Auto-accept changes
coder = Coder.create(
main_model=model,
fnames=["src/api/users.ts", "src/api/users.test.ts"],
io=io,
auto_commits=True,
auto_lint=True,
lint_cmds={"typescript": "npx eslint --fix"},
)
coder.run("Add pagination support to the listUsers endpoint. Use cursor-based pagination with a default page size of 20.")
```
## Installation
```bash
pip install aider-chat
# Set ANTHROPIC_API_KEY or OPENAI_API_KEY
```
## Best Practices
1. **Add only relevant files** — Don't add the whole project; add files Aider needs to edit plus key context files
2. **Read-only context** — Use `--read` for files Aider should understand but not edit (schemas, types, conventions)
3. **Diff format** — Use `edit-format: diff` for large files; `whole` for small files where full rewrites are fine
4. **Auto-lint + auto-test** — Enable both; Aider will fix lint errors and ensure tests pass before committing
5. **Repo map** — Aider builds a map of your codebase for context; increase `map-tokens` for large projects
6. **Git integration** — Aider commits each change; use `git diff` and `git log` to review AI changes
7. **Specific prompts** — "Fix the pagination bug in posts.ts" beats "fix bugs"; be specific about files and behavior
8. **Convention files** — Add CONVENTIONS.md or .cursor/rules as read-only context; Aider follows documented patterns
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.