Analyze errors: Review logs, error messages, and stack traces to identify the module or method where the failure occurs.
Isolate tests: Run only the failing tests separately to minimize noise and focus on the specific scenario.
Study tests: Examine the test code, comments, and descriptions to understand the expected behavior.
Review codebase: Locate the relevant sections of the code being tested and consult documentation, READMEs, or comments to grasp the overall architecture.
Reproduce issue: Create a minimal example that replicates the error to determine if it depends on specific data or configuration.
Create hypothesis: Identify the most likely root cause of the error.
Test hypothesis: Methodically test the hypothesis, making small, incremental changes and documenting each step.
If the hypothesis is incorrect, create a new one and test it again.
If the hypothesis is correct, make the minimal changes to the code to fix the error.
Verify: Run the full test suite to confirm the fix and ensure no regressions.

Más de este repositorio

mismo repositorio

Analyze and answer user questions in Autonomous Mode by reading documentation and inspecting codebase

Automated commit workflow with atomic grouping

Initialize project with AGENTS.md and rules, handling both Greenfield (new) and Brownfield (existing) projects.

Iterative issue investigation with user-controlled hypothesis selection

Perform a comprehensive "Lead Engineer" audit: structure, consistency, code quality, technical debt, documentation coverage, and terminology checks.

Create critiqued plan in whiteboard.md using GODS framework with proactive uncertainty resolution

name	flow-skill-fix-tests
description	How to fix tests

Analyze errors: Review logs, error messages, and stack traces to identify the module or method where the failure occurs.
Isolate tests: Run only the failing tests separately to minimize noise and focus on the specific scenario.
Study tests: Examine the test code, comments, and descriptions to understand the expected behavior.
Review codebase: Locate the relevant sections of the code being tested and consult documentation, READMEs, or comments to grasp the overall architecture.
Reproduce issue: Create a minimal example that replicates the error to determine if it depends on specific data or configuration.
Create hypothesis: Identify the most likely root cause of the error.
Test hypothesis: Methodically test the hypothesis, making small, incremental changes and documenting each step.
If the hypothesis is incorrect, create a new one and test it again.
If the hypothesis is correct, make the minimal changes to the code to fix the error.
Verify: Run the full test suite to confirm the fix and ensure no regressions.