GitHub Issues → Auto-Code → PR

{
  "schedules": [
    {
      "name": "issue-worker",
      "cron": "*/15 * * * *",
      "actions": [
        "poll-assigned-issues",
        "analyze-issue",
        "write-code",
        "run-tests",
        "open-pr",
        "request-review"
      ]
    }
  ],
  "integrations": {
    "github": {
      "repos": ["your-org/your-repo"],
      "assignee": "openclaw-bot",
      "triggerLabels": ["good-first-issue", "openclaw"],
      "pr": {
        "reviewers": ["your-username"],
        "draft": false,
        "branchPrefix": "openclaw/"
      }
    },
    "coding": {
      "tool": "opencode",
      "maxIterations": 3,
      "requireTests": true
    }
  }
}

## Issue Worker Rules
- Only pick up issues that are clearly scoped with acceptance criteria. If an issue is vague, add a comment asking for clarification instead of guessing.
- Before writing code, read the existing codebase patterns. Match the style, conventions, and test patterns already in use.
- Always create a new branch from the latest main. Never push directly to main.
- If tests fail after your changes, iterate up to maxIterations times. If still failing, open the PR as a draft with a comment explaining what's blocking.
- PR descriptions should reference the issue number, explain the approach taken, and note any tradeoffs.
- If an issue requires changes to more than 5 files, flag it as potentially too complex for automation and leave a comment.
- After opening the PR, wait for review feedback. If changes are requested, address them and push updates to the same branch.