Skip to content
Skills Library
Programming · Building & coding

aider-cli-workflow

/aider-cli-workflow

Runs a scope-locked, test-backed Aider coding loop with commit hygiene; use for local-repo AI pair-programming on one small feature or bug.

Repository
jeo-skills ↗
Licence
MIT
Last repository change
13.11.2026

Assessment and security

95/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene10 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
2
Deprecation

No signals detected. Repository changed on 13.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Runs a scope-locked, test-backed Aider coding loop with commit hygiene; use for local-repo AI pair-programming on one small feature or bug.

Original author description

Runs a scope-locked, test-backed Aider coding loop with commit hygiene; use for local-repo AI pair-programming on one small feature or bug.

How it works

  1. When to use this skill
  2. When not to use
  3. Instructions
  4. Output format
  5. Examples
  6. Best practices
  7. References
Original SKILL.md headings · 87 lines, 350 words
SKILL.md preview
---
name: aider-cli-workflow
description: >-
  Runs a scope-locked, test-backed Aider coding loop with commit hygiene; use for local-repo AI
  pair-programming on one small feature or bug.
allowed-tools: Bash Read Write Edit Glob Grep
metadata:
  tags: aider, cli, ai-pair-programming, git, test-driven, code-review
  platforms: Claude, Codex, Gemini, OpenCode
  source: akillness/jeo-skills
  version: 1.0.0
---












# Aider CLI Workflow

Use this skill when the user explicitly wants an **Aider-based coding loop** in a local repo.

## When to use this skill
- Aider 설치/초기 설정 확인부터 실행까지 한번에 정리해야 할 때
- 작은 기능/버그를 테스트 기준으로 AI pair-programming으로 처리할 때
- Aider가 만든 변경을 커밋 단위로 검증/정리해야 할 때

## When not to use
- Hosted PR 리뷰/라벨/브랜치 보호 정책 중심 작업 (`code-review`, GitHub workflow 계열)
- 단순 Git 충돌/복구만 필요한 경우 (`git-workflow`)
- 루트 원인 디버깅 중심 작업 (`debugging`)

## Instructions

### Step 1) Preconditions
1. 저장소 루트 확인: `git rev-parse --show-toplevel`
2. Aider 설치 확인: `aider --version`
3. 기본 검증 명령 확인: 테스트/린트 명령 1개 이상 확보

### Step 2) Scope-lock kickoff
- 한 번에 한 작업(버그 1개/기능 1개)만 지정한다.
- Aider 프롬프트에 반드시 포함:
  - 변경 대상 파일 범위
  - 수용 기준(acceptance criteria)
  - 테스트/검증 명령

### Step 3) Test-backed edit loop
1. 기준 테스트 실행(실패/성공 기준선 확보)
2. Aider로 수정
3. 테스트 재실행
4. diff 확인 후 필요 시 추가 수정

### Step 4) Commit hygiene
- `git add -p`로 변경 범위를 검토
- 커밋 메시지는 의도 + 검증 명령을 포함
- 리스크(실험적 패치, flaky test, 미검증 경로)는 커밋/보고서에 명시

### Step 5) Fallback
- 변경이 과도하게 퍼지면 즉시 범위를 축소하고 재시도
- 테스트가 반복적으로 깨지면 Aider 자동 수정 루프를 멈추고 원인 분석으로 전환

## Output format
```markdown
# Aider Run Brief
- Goal:
- Scope:
- Validation commands:
- Changed files:
- Risks / follow-ups:
```

## Examples

### Example 1: small bugfix loop
- Goal: failing unit test 1개를 green으로 복구
- Scope: 테스트 파일 + 관련 구현 파일만 편집
- Validation: `pytest -q tests/path/test_x.py`

### Example 2: narrow feature increment
- Goal: API 필드 1개 추가 + 역호환 유지
- Scope: schema + handler + 테스트
- Validation: 기존 테스트 + 신규 테스트

## Best practices
1. 항상 baseline 테스트 결과를 먼저 확보한다.
2. 파일 범위를 명시하지 않은 Aider 세션은 시작하지 않는다.
3. 커밋 전에 `git add -p`로 불필요 변경을 제거한다.
4. flaky/실험적 변경은 리스크를 명시하고 후속 TODO를 남긴다.

## References
- Aider: https://github.com/Aider-AI/aider
- Aider docs: https://aider.chat/

Versions

The database has no other skills named aider-cli-workflow.

Database snapshot: 13.11.2026 · package version 7b19525b3549 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100aider-delegate
    Delegate a coding task to Aider (`aider`) as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to hand implementation work to Aider - phrasings like "have Aider do X", "delegate this to aider", "run it through Aider", or "use…
  • 100aider-delegate
    Delegate coding tasks to Aider (`aider`) only when the user explicitly requests it, while the orchestrator retains review and landing responsibility.
  • 100aider-delegate
    Delegate coding tasks to Aider (`aider`) only when the user explicitly requests it, while the orchestrator retains review and landing responsibility.
  • 100vibe-coding
    AI-assisted coding with Claude Code, Cursor, Copilot, Codex, Aider, or Windsurf. Use to build or debug generated code.
  • 100vibe-coding
    Patterns and workflows for AI-assisted development (vibe coding) — building software primarily through natural language with AI coding agents. Use when: setting up an AI-first development workflow, structuring projects for AI coding, using prompt-driven development best…
  • 100repo-hygiene
    Use when the scheduled repo-hygiene workflow runs from GitHub Actions (or an operator dry-run) to scan the repository for small, certain docs/test/code hygiene issues and fix them as one batched branch.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.