From e2c99905546f4f0a8f13d3bfc3cb7f2c570aaf77 Mon Sep 17 00:00:00 2001 From: promptadmin Date: Sat, 6 Jun 2026 20:32:34 +0000 Subject: [PATCH] Automated ingestion of prompt: Test-First Bug Fixing Approach --- prompts/coding/test_first_bug_fixing_approach_1271.md | 7 +++++++ 1 file changed, 7 insertions(+) create mode 100644 prompts/coding/test_first_bug_fixing_approach_1271.md diff --git a/prompts/coding/test_first_bug_fixing_approach_1271.md b/prompts/coding/test_first_bug_fixing_approach_1271.md new file mode 100644 index 0000000..7dbfbab --- /dev/null +++ b/prompts/coding/test_first_bug_fixing_approach_1271.md @@ -0,0 +1,7 @@ +--- +title: "Test-First Bug Fixing Approach" +contributor: "@ilkerulusoy" +tags: #coding, #ilkerulusoy +--- + +I have a bug: ${bug}. Take a test-first approach: 1) Read the relevant source files and existing tests. 2) Write a failing test that reproduces the exact bug. 3) Run the test suite to confirm it fails. 4) Implement the minimal fix. 5) Re-run the full test suite. 6) If any test fails, analyze the failure, adjust the code, and re-run—repeat until ALL tests pass. 7) Then grep the codebase for related code paths that might have the same issue and add tests for those too. 8) Summarize every change made and why. Do not ask me questions—make reasonable assumptions and document them.