Updated 3d ago
by dan-the-dev
xp-developer-skills
A series of skills for AI coding agents to amplify XP practices.
32 GitHub stars (32)
+2 in 16 days
| Period | New stars |
|---|---|
| Oct 1 | 0 |
| Oct 2 | 0 |
| Oct 3 | 0 |
| Oct 4 | 0 |
| Oct 5 | 0 |
| Oct 6 | 0 |
| Oct 7 | 0 |
| Oct 8 | 0 |
| Oct 9 | 0 |
| Oct 10 | 0 |
| Oct 11 | 0 |
| Oct 12 | 0 |
| Oct 13 | +1 |
| Oct 14 | 0 |
| Oct 15 | +1 |
| Oct 16 | 0 |
- 10 skills (10 skills found in its SKILL.md files)
- 1 forks (1 forks)
- 3d ago last update (Last updated 3d ago)
Install
Skills CLI
npx skills add dan-the-dev/xp-developer-skills
Asks which skills and agents to install. Just one: npx skills add dan-the-dev/xp-developer-skills --skill atdd — add -g for every project.
Claude Code
git clone https://github.com/dan-the-dev/xp-developer-skillscp -r "xp-developer-skills/skills/atdd" ~/.claude/skills/
Copies the atdd skill into ~/.claude/skills/ for every project (use .claude/skills/ for one project). Repeat for the other skills listed below.
Plugin
/plugin marketplace add dan-the-dev/xp-developer-skills
Run inside Claude Code if the repository ships a plugin marketplace, then pick plugins from /plugin.
Skills can run code on your machine — read the SKILL.md first.
What it does
In the author's own words, from each skill's SKILL.md.
-
atdd
Pragmatic Acceptance Test-Driven Development — agree concrete examples with stakeholders (Discuss), capture them as executable acceptance checks (Distill), then implement with outside-in delivery (Develop). Works in two modes — API-only (HTTP/CLI/event/in-process seam, the default) or E2E (browser, full stack, Page Objects) — with Gherkin/Cucumber when it helps, code-first acceptance tests, and c…
skills/atdd/SKILL.md on GitHub (opens in a new tab) -
bugfix
Use when fixing bugs, regressions, failing tests, or unexpected behavior. Applies a strict test-first bugfix workflow with minimal safe changes, isolated commits, and language-agnostic verification strategies.
skills/bugfix/SKILL.md on GitHub (opens in a new tab) -
increment-review
Fast, single-pass review of one just-finished increment — target under 60 seconds of work. Reads the new-increment mini-journal and that increment's diff only, checks against docs/code-review.md, and returns approved / changes-requested / bug-found with a short targeted fix brief. This is the default reviewer new-feature invokes after new-increment — not skills/refactoring directly. Use immediate…
skills/increment-review/SKILL.md on GitHub (opens in a new tab) -
legacy-testing
Michael Feathers–style legacy code change — treat code without automated tests as legacy, then follow identify change points, find test points, break dependencies, add tests (often characterization), and only then modify or refactor. Covers seams (object/link/preprocessing), sensing vs separation, fakes/mocks, sprout/wrap, pinch points, effect sketches, and dependency-breaking patterns. Composes…
skills/legacy-testing/SKILL.md on GitHub (opens in a new tab) -
new-feature
Slice a whole capability into ordered releasable increments (increment backlog in increments/<stem>.md). Delegate each slice to skills/new-increment, review via skills/increment-review — do not implement slices or review them yourself. Confirms the plan before executing (wait in step mode, ~2min pause in automatic). Default step mode stops after each increment for feedback; automatic mode (explic…
skills/new-feature/SKILL.md on GitHub (opens in a new tab) -
new-increment
Deliver one releasable increment from increments/<feature>.md — strict TDD by default (one test-lists/<feature>.md, unit tests). ATDD only when a real outer seam exists (API/UI/contract). One increment per invocation; RED before GREEN; all project verify steps green before done; commit then stop. Not for whole-feature planning (skills/new-feature).
skills/new-increment/SKILL.md on GitHub (opens in a new tab) -
refactoring
Martin Fowler–style refactoring — change the internal structure of code without changing observable behavior. Baby steps on a green baseline: one mechanical transformation at a time, tests stay green, revert on red. Also executes an increment-review fix brief, or runs the legacy manual post-increment review mode on direct user request (explain commits, suggest small in-scope refactors/tests) — sk…
skills/refactoring/SKILL.md on GitHub (opens in a new tab) -
spike
XP-style spike — time-boxed experiment on an isolated branch; code is disposable. Answer one technical or design question (feasibility, library fit, performance bound, integration). Use automated checks only when they help prove the goal — no delivery test pyramid, no ATDD/TDD discipline on the spike branch. Explicit promotion to skills/atdd, skills/tdd, or skills/legacy-testing when learning is…
skills/spike/SKILL.md on GitHub (opens in a new tab) -
tdd
Applies strict Test-Driven Development with a repo-local Markdown test list (default `test-lists/<slug>.md` unless the project defines another folder), Robert C. Martin’s Three Laws, deterministic tests and stable seams (unit vs narrow integration), Arrange–Act–Assert test shape, micro-iterations, refactor proximity (production and test code), fast feedback, and git micro-commits (`test:` / `feat…
skills/tdd/SKILL.md on GitHub (opens in a new tab) -
tweak
Small, targeted change to the feature already on the current branch — copy/text, a color or style, a small logic change, or a small new file. Scoped edit, scoped tests, scoped lint, one commit on the current branch. No increments file, no feature branch, no PR. Use for a quick follow-up tweak right after new-feature/new-increment finished, not for a new capability or a multi-file feature (use ski…
skills/tweak/SKILL.md on GitHub (opens in a new tab)
No skill matches that filter.
Review before you install
A skill is a set of instructions and scripts your agent will follow, and it can run code on your machine. Read the SKILL.md and any scripts first — this listing is not a security review.