tdd-london-chicago
About
This Claude Skill helps developers apply both London (mock-based) and Chicago (state-based) TDD approaches when practicing test-driven development. It guides you to choose the appropriate style based on your context—using Chicago for domain logic and London for code with external dependencies. The skill follows the red-green-refactor cycle and works with specialized testing agents to generate, implement, and refactor tests.
Quick Install
Claude Code
Recommendednpx skills add proffesor-for-testing/agentic-qe -a claude-code/plugin add https://github.com/proffesor-for-testing/agentic-qegit clone https://github.com/proffesor-for-testing/agentic-qe.git ~/.claude/skills/tdd-london-chicagoCopy and paste this command in Claude Code to install this skill
GitHub Repository
Related Skills
refactoring-patterns
OtherThis Claude Skill applies safe refactoring patterns to improve code structure while preserving existing behavior. It's designed for cleaning up code, reducing technical debt, and enhancing maintainability through a disciplined test-first approach. The skill emphasizes small, incremental changes with continuous testing to ensure reliability during code transformations.
code-review-quality
OtherThis skill conducts automated code reviews focused on quality, testability, and maintainability, prioritizing critical feedback like bugs and security issues. It's designed for use during code reviews, when providing feedback, or when establishing review practices. The tool categorizes feedback by severity and emphasizes asking questions over issuing commands.
code-review-quality
OtherThis Claude Skill performs context-driven code reviews focused on code quality, testability, and maintainability. It prioritizes actionable feedback on bugs, security, and design over style preferences, using a structured severity system. Developers should use it when reviewing code, providing feedback, or establishing team review practices.
code-review-quality
OtherThis Claude Skill performs automated code reviews focused on quality, testability, and maintainability. It prioritizes actionable feedback on bugs, security, and maintainability over style preferences, using a tiered severity system. Developers should use it when reviewing code, providing feedback, or establishing review practices.