Results for “refactoring”

Refactors production code with test coverage using a TDD workflow that applies approved refactorings one at a time, gates each on passing tests, and commits or reverts accordingly.

Coordinates five specialized coding agents (linter, perf, refactor, security, test) to enforce quality gates across the development lifecycle, from lint enforcement through performance profiling, refactoring, security auditing, and test coverage.

Write readable, maintainable code through disciplined naming, small functions, and clean error handling.

Guides test-driven development with a red-green-refactor loop, emphasizing behavior-focused tests and vertical slicing over horizontal test writing.

Guides writing a failing test before production code, iterating through red-green-refactor cycles, and fixing bugs test-first.

Delivers changes incrementally by building in thin vertical slices, testing and verifying each piece before moving to the next.

Migrate test files from `as` type assertions to @total-typescript/shoehorn, using fromPartial and fromAny for partial or intentionally wrong test data.

Refactors test files to improve behavioral coverage, clarity, structure, assertions, fixture setup, and mocking strategy, removing implementation-detail or low-value tests.

Implements features, fixes bugs, and refactors code by orchestrating domain-specific skills, following existing patterns, and verifying tests and lint pass.

Reviews a codebase for structural smells and refactors them with provable safety, using micro commits and green-bar discipline.

Migrate Pester v5 classic Should -Be assertion syntax to the new Pester v6 Should-* operators with a step-by-step mapping and behavioral gotchas.

Drive development with tests by writing a failing test before implementing code, and reproduce bugs with tests before fixing them.

Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests for new features, bug fixes, or refactoring.

Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests for new features, bug fixes, and refactoring.

Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests when writing features, fixing bugs, or refactoring code.

Defines a gated Research-Plan-TDD-Review-Commit pipeline for orchestrating feature development, defect fixes, and refactoring tasks through composable phases and human approval gates.

Orchestrate altering an existing, working feature to new desired behavior by updating tests first, then changing implementation, reviewing, and committing with gated approval.

Automatically detects project state and runs an 8-phase pipeline to plan, build, test, lint, fix bugs, and document code across multiple AI coding agents.

Safely change and test untested codebases using techniques from Feathers' 'Working Effectively with Legacy Code': seams, characterization tests, sprout/wrap, and dependency-breaking.

Test-driven development for Quarkus 3.x LTS using JUnit 5, Mockito, REST Assured, Camel testing, and JaCoCo. Use when adding features, fixing bugs, or refactoring event-driven services.

Finds and safely removes dead code across a codebase: unreachable paths, unused exports, functions, variables, CSS selectors, dependencies, env vars, and commented-out blocks. Builds an import graph, verifies no dynamic references, and runs build and tests after cleanup.

Enforces strict outside-in red-green-refactor TDD with one-failure-per-turn discipline, predicting failures before every run, hardcoding minimum changes, and using triangulation and property-based testing. Triggers on explicit TDD requests and tasks phrased as 'implement', 'add', 'write a function', 'build a feature'.