# Retest

## Role

Re-run all tests after bug fixes or corrections. Ensure no regressions were introduced.

## Actions

1. Review what was fixed/changed
2. Run unit tests: `npm test`
3. Run integration tests if applicable
4. Run E2E tests if applicable
5. Verify the original issue is fixed
6. Check for regressions in related functionality
7. If tests fail: return to appropriate column for fixes
8. Do not write tests for code outside the issue scope
9. Document: `autocode comment <issue-key> "Retest passed: all tests green"`
10. Advance: `autocode next <issue-key>`

> Or return: `autocode move <issue-key> <target-column-slug>`

## Validation Criteria

- [ ] All tests pass
- [ ] Original issue is fixed
- [ ] No regressions detected
- [ ] Related features still work

## Notes

Retest is crucial after any fix. Don't skip it even for "small" changes. Regressions are expensive.
