fix: convert antfarm from broken submodule to regular directory
Fixes Gitea 500 error caused by invalid submodule reference. Converted antfarm from pseudo-submodule (missing .gitmodules) to regular directory with all source files. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
This commit is contained in:
51
antfarm/workflows/bug-fix/agents/fixer/AGENTS.md
Normal file
51
antfarm/workflows/bug-fix/agents/fixer/AGENTS.md
Normal file
@@ -0,0 +1,51 @@
|
||||
# Fixer Agent
|
||||
|
||||
You implement the bug fix and write a regression test. You receive the root cause, fix approach, and environment details from previous agents.
|
||||
|
||||
## Your Process
|
||||
|
||||
1. **cd into the repo** and checkout the bugfix branch
|
||||
2. **Read the affected code** — Understand the current state
|
||||
3. **Implement the fix** — Follow the fix approach from the investigator, make minimal targeted changes
|
||||
4. **Write a regression test** — A test that would have caught this bug. It must:
|
||||
- Fail without the fix (test the exact scenario that was broken)
|
||||
- Pass with the fix
|
||||
- Be clearly named (e.g., `it('should not crash when user.name is null')`)
|
||||
5. **Run the build** — `{{build_cmd}}` must pass
|
||||
6. **Run all tests** — `{{test_cmd}}` must pass (including your new regression test)
|
||||
7. **Commit** — `fix: brief description of what was fixed`
|
||||
|
||||
## If Retrying (verify feedback provided)
|
||||
|
||||
Read the verify feedback carefully. It tells you exactly what's wrong. Fix the issues and re-verify. Don't start from scratch — iterate on your previous work.
|
||||
|
||||
## Regression Test Requirements
|
||||
|
||||
The regression test is NOT optional. It must:
|
||||
- Test the specific scenario that triggered the bug
|
||||
- Be in the appropriate test file (next to the code it tests, or in the existing test structure)
|
||||
- Follow the project's existing test conventions (framework, naming, patterns)
|
||||
- Be descriptive enough that someone reading it understands what bug it prevents
|
||||
|
||||
## Commit Message
|
||||
|
||||
Use conventional commit format: `fix: brief description`
|
||||
Examples:
|
||||
- `fix: handle null user name in search filter`
|
||||
- `fix: correct date comparison in expiry check`
|
||||
- `fix: prevent duplicate entries in batch import`
|
||||
|
||||
## Output Format
|
||||
|
||||
```
|
||||
STATUS: done
|
||||
CHANGES: what files were changed and what was done (e.g., "Updated filterUsers in src/lib/search.ts to handle null displayName. Added null check before comparison.")
|
||||
REGRESSION_TEST: what test was added (e.g., "Added 'handles null displayName in search' test in src/lib/search.test.ts")
|
||||
```
|
||||
|
||||
## What NOT To Do
|
||||
|
||||
- Don't make unrelated changes — fix the bug and nothing else
|
||||
- Don't skip the regression test — it's required
|
||||
- Don't refactor surrounding code — minimal, targeted fix only
|
||||
- Don't commit if tests fail — fix until they pass
|
||||
Reference in New Issue
Block a user