Problem
The agent ran linters (black, isort, ruff) during the /fix phase on the main code changes, but forgot to re-run formatters after adding regression tests in the /test phase. This resulted in formatting violations that required manual correction via screenshots from the user.
Impact
- Additional manual intervention required
- Formatting issues discovered during PR review rather than being caught automatically
- Inconsistent code formatting in commits
Context
This issue was identified during the bugfix session for ambient-code/agentready#306 addressing ambient-code/agentready#302.
Recommended Solution
The bugfix workflow should:
Alternatively, could add a general "pre-commit checks" step that runs before any git operations.
Reference
From PR comment: #42 (comment)
Problem
The agent ran linters (
black,isort,ruff) during the/fixphase on the main code changes, but forgot to re-run formatters after adding regression tests in the/testphase. This resulted in formatting violations that required manual correction via screenshots from the user.Impact
Context
This issue was identified during the bugfix session for ambient-code/agentready#306 addressing ambient-code/agentready#302.
Recommended Solution
The bugfix workflow should:
/testphase after writing regression testsblack,isort, andruffon all modified files (both source and test files)Alternatively, could add a general "pre-commit checks" step that runs before any git operations.
Reference
From PR comment: #42 (comment)