2026-03-12 13:04:50 +00:00
|
|
|
# Dev-Agent Best Practices
|
|
|
|
|
|
|
|
|
|
## Architecture
|
|
|
|
|
- `dev-poll.sh` (cron */10) → finds ready backlog issues → spawns `dev-agent.sh`
|
|
|
|
|
- `dev-agent.sh` uses `claude -p` for implementation, runs in git worktree
|
|
|
|
|
- Lock file: `/tmp/dev-agent.lock` (contains PID)
|
|
|
|
|
- Status file: `/tmp/dev-agent-status`
|
|
|
|
|
- Worktrees: `/tmp/harb-worktree-<issue-number>/`
|
|
|
|
|
|
|
|
|
|
## Safe Fixes
|
|
|
|
|
- Remove stale lock: `rm -f /tmp/dev-agent.lock` (only if PID is dead)
|
|
|
|
|
- Kill stuck agent: `kill <pid>` then clean lock
|
|
|
|
|
- Restart on derailed PR: `bash ${FACTORY_ROOT}/dev/dev-agent.sh <issue-number> &`
|
|
|
|
|
- Clean worktree: `cd /home/debian/harb && git worktree remove /tmp/harb-worktree-<N> --force`
|
|
|
|
|
- Remove `in-progress` label if agent died without cleanup:
|
|
|
|
|
```bash
|
|
|
|
|
codeberg_api DELETE "/issues/<N>/labels/in-progress"
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
## Dangerous (escalate)
|
|
|
|
|
- Restarting agent on an issue that has an open PR with review changes — may lose context
|
|
|
|
|
- Anything that modifies the PR branch history
|
|
|
|
|
- Closing PRs or issues
|
|
|
|
|
|
|
|
|
|
## Known Issues
|
|
|
|
|
- `claude -p -c` (continue) fails if session was compacted — falls back to fresh `-p`
|
|
|
|
|
- CI_FIX_COUNT is now reset on CI pass (fixed 2026-03-12), so each review phase gets fresh CI fix budget
|
|
|
|
|
- Worktree creation fails if main repo has stale rebase — auto-heals now
|
|
|
|
|
- Large text in jq `--arg` can break — write to file first
|
|
|
|
|
- `$([ "$VAR" = true ] && echo "...")` crashes under `set -euo pipefail`
|
|
|
|
|
|
|
|
|
|
## Lessons Learned
|
|
|
|
|
- Agents don't have memory between tasks — full context must be in the prompt
|
|
|
|
|
- Prior art injection (closed PR diffs) prevents rework
|
|
|
|
|
- Feature issues MUST list affected e2e test files
|
|
|
|
|
- CI fix loop is essential — first attempt rarely works
|
|
|
|
|
- CLAUDE_TIMEOUT=7200 (2h) is needed for complex issues
|
2026-03-13 11:26:52 +00:00
|
|
|
|
|
|
|
|
## Dependency Resolution
|
|
|
|
|
|
|
|
|
|
**Trust closed state.** If a dependency issue is closed, the code is on master. Period.
|
|
|
|
|
|
|
|
|
|
DO NOT try to find the specific PR that closed an issue. This is over-engineering that causes false negatives:
|
|
|
|
|
- Codeberg shares issue/PR numbering — no guaranteed relationship
|
|
|
|
|
- PRs don't always mention the issue number in title/body
|
|
|
|
|
- Searching last N closed PRs misses older merges
|
|
|
|
|
- The factory itself closes issues after merging, so closed = merged
|
|
|
|
|
|
|
|
|
|
The only check needed: `issue.state == "closed"`.
|
