patch-implementer

Implement minimal test-driven bug fixes with explicit file edits and regression verification.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/yuridefranca/ai-prompts --skill patch-implementer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: patch-implementer
Source: https://github.com/yuridefranca/ai-prompts/tree/main/src/skills/patch-implementer
Command: npx skills add https://github.com/yuridefranca/ai-prompts --skill patch-implementer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Implements minimal, test-driven bug fixes that directly address critique feedback and edge cases while ensuring changes are applied to repository files and verified by tests rather than left as chat suggestions.

Core Features & Use Cases

  • TDD-first workflow: Create or update failing tests that reproduce the bug, implement the smallest change to pass them, then verify no regressions.
  • Engineer handoff pattern: Produce precise instructions for engineer agents including file paths, editing operations, and required tests to run.
  • Verification and documentation: Run targeted and full test suites, document root cause and changes, and keep commits minimal and focused.
  • Use Case: After a solution critic identifies a null-pointer crash in a user email parser, use this Skill to add failing tests that reproduce the crash, instruct an engineer to apply the minimal null check fix, and confirm all tests pass.

Quick Start

Use the patch-implementer after solution-critic feedback to create failing tests, instruct an engineer agent to apply the minimal file edits, and run the test suite to confirm the fix.

Frequently Asked Questions about patch-implementer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement a minimal bug fix using test-driven development?

Minimal bug fixes using test-driven development involve creating failing tests that reproduce the bug, applying the smallest code change to pass them, and running test suites to confirm no regressions. This ensures fixes are verified rather than left as chat suggestions.

How do I create engineer handoff instructions for repository file edits?

Engineer handoff instructions for file edits specify exact file paths, required editing operations, and targeted tests to run. This pattern ensures engineer agents apply minimal changes correctly and verify fixes through executed test suites.

What is the best way to fix a bug after a solution critique identifies edge cases?

Fixing bugs after solution critique involves adding failing tests that cover identified edge cases, instructing an engineer to apply minimal code changes, and running targeted and full test suites to confirm the fix without introducing regressions.

Can I use TDD to fix a null-pointer crash in my backend repository?

Yes, TDD can fix null-pointer crashes in backend repositories by first adding a failing test that reproduces the crash, then applying a minimal null check fix, and finally confirming all tests pass without regressions.

How do I add edge case coverage and verify regressions when patching code?

Adding edge case coverage and verifying regressions requires creating failing tests for edge cases, performing minimal code changes to pass them, and executing targeted and full test suites to confirm no regressions in the repository.

What should I do if my bug fix suggestions are not being applied to repository files?

When bug fix suggestions are not applied to files, use an engineer handoff pattern that requires explicit repository file edits via file-editing tools and execution of targeted test suites to reproduce and confirm the applied fixes.