aider-delegate

Aider Delegate

When to Use

• You want to delegate a bounded coding task to a separate aider implementer (Aider) and then review its diff yourself.
• The user explicitly asked for delegation to this implementer.

You are the orchestrator. Hand a bounded coding task to a separate implementer - Aider - then review what it produced and land it yourself. You write the brief and own the judgment; Aider does the typing in its own run; you verify and commit.

The loop needs only a shell command and file access, so any comparable orchestrator can drive it.

The one thing to know about Aider

Aider commits by default. Two of its defaults would destroy the reviewable diff this skill exists to produce:

• --auto-commits (default True) - Aider commits its own edits after each exchange.
• --dirty-commits (default True) - Aider commits your pre-existing uncommitted work before it starts editing.

The relay always passes --no-auto-commits and --no-dirty-commits, and neither is configurable through it. If you ever drive aider by hand instead of through the relay, pass both yourself, or the work lands as commits you never reviewed. The relay also passes --no-gitignore, because Aider otherwise writes .aider* into .gitignore on startup and dirties the tree you are about to read.

When NOT to use this

• The task is small enough to do inline; delegation overhead is not worth it.
• The aider CLI is not installed, or no model is configured for it.
• You want the implementer to manage its own commits. Aider can, but this skill deliberately turns that off - the diff is the deliverable.

Prerequisites (check once)

1. Install Aider - python -m pip install aider-chat, or the standalone installer from the Aider install docs.
2. Configure a model. Aider reads provider keys from the environment (OPENAI_API_KEY, ANTHROPIC_API_KEY, …) or its own config; see Aider's model docs.
3. Confirm aider --version succeeds.
4. Work in, or point --cd at, the target git repository.