tessl-eval-demo

Investigates a test failure, bug, or unexpected behavior to find its root cause before proposing any fix - reproduce the issue, trace the data flow, form and test one hypothesis at a time, then implement and verify the fix. This is the debugging stage inside the delivery-flow workflow, entered by requests like "debug this failure", "why is this test failing", "find the root cause", or "this bug keeps coming back" once delivery-flow has handed off a bug. Do not activate directly for a standalone bug report that has not gone through delivery-flow first.

Investigates a test failure, bug, or unexpected behavior to find its root cause before proposing any fix - reproduce the issue, trace the data flow, form and test one hypothesis at a time, then implement and verify the fix. This is the debugging stage inside the delivery-flow workflow, entered by requests like "debug this failure", "why is this test failing", "find the root cause", or "this bug keeps coming back" once delivery-flow has handed off a bug. Do not activate directly for a standalone bug report that has not gone through delivery-flow first.

Investigates a test failure, bug, or unexpected behavior to find its root cause before proposing any fix - reproduce the issue, trace the data flow, form and test one hypothesis at a time, then implement and verify the fix. This is the debugging stage inside the delivery-flow workflow, entered by requests like "debug this failure", "why is this test failing", "find the root cause", or "this bug keeps coming back" once delivery-flow has handed off a bug. Do not activate directly for a standalone bug report that has not gone through delivery-flow first.

Investigates a test failure, bug, or unexpected behavior to find its root cause before proposing any fix - reproduce the issue, trace the data flow, form and test one hypothesis at a time, then implement and verify the fix. This is the debugging stage inside the delivery-flow workflow, entered by requests like "debug this failure", "why is this test failing", "find the root cause", or "this bug keeps coming back" once delivery-flow has handed off a bug. Do not activate directly for a standalone bug report that has not gone through delivery-flow first.

Investigates a test failure, bug, or unexpected behavior to find its root cause before proposing any fix - reproduce the issue, trace the data flow, form and test one hypothesis at a time, then implement and verify the fix. This is the debugging stage inside the delivery-flow workflow, entered by requests like "debug this failure", "why is this test failing", "find the root cause", or "this bug keeps coming back" once delivery-flow has handed off a bug. Do not activate directly for a standalone bug report that has not gone through delivery-flow first.

Investigates a test failure, bug, or unexpected behavior to find its root cause before proposing any fix - reproduce the issue, trace the data flow, form and test one hypothesis at a time, then implement and verify the fix. This is the debugging stage inside the delivery-flow workflow, entered by requests like "debug this failure", "why is this test failing", "find the root cause", or "this bug keeps coming back" once delivery-flow has handed off a bug. Do not activate directly for a standalone bug report that has not gone through delivery-flow first.

Investigates a test failure, bug, or unexpected behavior to find its root cause before proposing any fix - reproduce the issue, trace the data flow, form and test one hypothesis at a time, then implement and verify the fix. This is the debugging stage inside the delivery-flow workflow, entered by requests like "debug this failure", "why is this test failing", "find the root cause", or "this bug keeps coming back" once delivery-flow has handed off a bug. Do not activate directly for a standalone bug report that has not gone through delivery-flow first.

Investigates a test failure, bug, or unexpected behavior to find its root cause before proposing any fix - reproduce the issue, trace the data flow, form and test one hypothesis at a time, then implement and verify the fix. This is the debugging stage inside the delivery-flow workflow, entered by requests like "debug this failure", "why is this test failing", "find the root cause", or "this bug keeps coming back" once delivery-flow has handed off a bug. Do not activate directly for a standalone bug report that has not gone through delivery-flow first.

Investigates a test failure, bug, or unexpected behavior to find its root cause before proposing any fix - reproduce the issue, trace the data flow, form and test one hypothesis at a time, then implement and verify the fix. This is the debugging stage inside the delivery-flow workflow, entered by requests like "debug this failure", "why is this test failing", "find the root cause", or "this bug keeps coming back" once delivery-flow has handed off a bug. Do not activate directly for a standalone bug report that has not gone through delivery-flow first.

Investigates a test failure, bug, or unexpected behavior to find its root cause before proposing any fix - reproduce the issue, trace the data flow, form and test one hypothesis at a time, then implement and verify the fix. This is the debugging stage inside the delivery-flow workflow, entered by requests like "debug this failure", "why is this test failing", "find the root cause", or "this bug keeps coming back" once delivery-flow has handed off a bug. Do not activate directly for a standalone bug report that has not gone through delivery-flow first.

Investigates a test failure, bug, or unexpected behavior to find its root cause before proposing any fix - reproduce the issue, trace the data flow, form and test one hypothesis at a time, then implement and verify the fix. This is the debugging stage inside the delivery-flow workflow, entered by requests like "debug this failure", "why is this test failing", "find the root cause", or "this bug keeps coming back" once delivery-flow has handed off a bug. Do not activate directly for a standalone bug report that has not gone through delivery-flow first.

Investigates a test failure, bug, or unexpected behavior to find its root cause before proposing any fix - reproduce the issue, trace the data flow, form and test one hypothesis at a time, then implement and verify the fix. This is the debugging stage inside the delivery-flow workflow, entered by requests like "debug this failure", "why is this test failing", "find the root cause", or "this bug keeps coming back" once delivery-flow has handed off a bug. Do not activate directly for a standalone bug report that has not gone through delivery-flow first.

Implements a feature or bug fix test-first: write one failing test, run it and watch it fail, write the minimal code to pass, then refactor with the tests green. Use when a change alters code behavior: a new feature, a bug fix, or a behavior change, whether the request comes alone or through delivery-flow.

Implements a feature or bug fix test-first: write one failing test, run it and watch it fail, write the minimal code to pass, then refactor with the tests green. Use when a change alters code behavior: a new feature, a bug fix, or a behavior change, whether the request comes alone or through delivery-flow.

Implements a feature or bug fix test-first: write one failing test, run it and watch it fail, write the minimal code to pass, then refactor with the tests green. Use when a change alters code behavior: a new feature, a bug fix, or a behavior change, whether the request comes alone or through delivery-flow.

Implements a feature or bug fix test-first: write one failing test, run it and watch it fail, write the minimal code to pass, then refactor with the tests green. Use when a change alters code behavior: a new feature, a bug fix, or a behavior change, whether the request comes alone or through delivery-flow.

Implements a feature or bug fix test-first - write one failing test, watch it fail, write the minimal code to pass, then refactor with tests green. This is the implementation stage inside the delivery-flow workflow, entered by requests like "implement this feature", "fix this bug", "write the code for this", or "add the tests and implement it" once delivery-flow is driving the change. Do not activate directly for a standalone request that has not gone through delivery-flow first.

Implements a feature or bug fix test-first: write one failing test, run it and watch it fail, write the minimal code to pass, then refactor with the tests green. Use when a change alters code behavior: a new feature, a bug fix, or a behavior change, whether the request comes alone or through delivery-flow.

Implements a feature or bug fix test-first: write one failing test, run it and watch it fail, write the minimal code to pass, then refactor with the tests green. Use when a change alters code behavior: a new feature, a bug fix, or a behavior change, whether the request comes alone or through delivery-flow.

Implements a feature or bug fix test-first: write one failing test, run it and watch it fail, write the minimal code to pass, then refactor with the tests green. Use when a change alters code behavior: a new feature, a bug fix, or a behavior change, whether the request comes alone or through delivery-flow.