task-completer

To ensure tasks meet the Definition of Done before merging, verify all acceptance criteria are satisfied, run the full test suite to prevent regressions, and align all documentation with the current code state.

A rigorous Definition of Done for software development includes verifying acceptance criteria, running test suites to check for side effects, eliminating loose ends like debug logs, and ensuring documentation accurately reflects the code.

You can verify acceptance criteria and prevent incomplete task finalization by enforcing quality standards that check requirements against the original request, run tests, and remove placeholder comments or temporary files.

Yes, task completion verification checks for code regressions and side effects by running the full test suite to confirm that no unrelated parts of the system have been broken during development.

The best way to remove loose ends like debug logs and temporary files before task completion is to enforce a checklist that eliminates placeholder comments and verifies documentation alignment with the current code.