Add QA testing step to task completion protocol
Before git commit, agents must now run pytest tests/ -v --tb=short to verify their changes don't break existing functionality. The protocol now: 1. Document Changes 2. Run Tests (NEW - required step) 3. Git Commit 4. Knowledge Graph This ensures code quality and prevents regressions. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
16
bin/luzia
16
bin/luzia
@@ -1285,13 +1285,25 @@ When you finish your work, you MUST complete these steps before ending:
|
||||
- Update README.md if user-facing features changed
|
||||
- Add comments to complex code sections
|
||||
|
||||
2. **Git Commit**: Commit your changes with a descriptive message:
|
||||
2. **Run Tests (REQUIRED)**: Before committing, verify your changes don't break existing functionality:
|
||||
```bash
|
||||
# Run project tests (if tests/ directory exists)
|
||||
if [ -d tests/ ]; then
|
||||
pytest tests/ -v --tb=short
|
||||
fi
|
||||
# If tests fail, FIX THE ISSUES before proceeding to commit
|
||||
```
|
||||
- If tests fail, debug and fix the failures
|
||||
- If you added new functionality, add corresponding tests
|
||||
- Update existing tests if your changes require test modifications
|
||||
|
||||
3. **Git Commit**: Commit your changes with a descriptive message:
|
||||
```bash
|
||||
git add -A
|
||||
git commit -m "Task: <brief description of what was done>"
|
||||
```
|
||||
|
||||
3. **Knowledge Graph**: Store key learnings using mcp__shared-projects-memory__store_fact
|
||||
4. **Knowledge Graph**: Store key learnings using mcp__shared-projects-memory__store_fact
|
||||
|
||||
Note: The project state was automatically snapshot before this task started.
|
||||
If you need to revert, the previous state can be recovered from git history."""
|
||||
|
||||
Reference in New Issue
Block a user