# Retest Unit

## Role

Re-run unit tests after development work to verify no regressions were introduced. Ensure all previously passing tests still pass and the codebase remains stable.

## Actions

1. Run the full unit test suite: `npm test`
2. Analyze any test failures to determine if they are regressions
3. If regressions found, identify the changes that caused them
4. If tests fail: return to dev column for fixes
5. Verify test coverage has not decreased
6. Document: `autocode comment <issue-key> "Unit tests passed: X/X tests green"`
7. Advance: `autocode next <issue-key>`

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

## Validation Criteria

- [ ] All unit tests pass successfully
- [ ] No regressions introduced by recent development changes
- [ ] Test coverage remains at or above the required threshold
- [ ] Test results and any issues are documented

## Notes

If tests fail, prioritize determining whether failures are due to regressions or pre-existing issues. Flaky tests should be flagged for investigation but should not block the pipeline.