shepherd

Use a polling loop that lists open PRs with gh pr list or glab mr list, then checks each for new comments by comparing timestamps against the previous poll. Triage each comment by type — approvals, change requests, nits, or questions — and act accordingly.

Fetch failing check logs with gh run view --log-failed, diagnose the root cause, and only push fixes that are small and obvious, such as lint or formatting errors. If the failure is ambiguous or requires domain knowledge, report it to the user instead of guessing.

Yes, the workflow detects the platform from the git remote URL and uses glab for GitLab and gh for GitHub. GitLab pipelines are inspected with glab ci list and glab ci trace, and manual pipeline stages are skipped.

Stop when a CI failure repeats across three cycles, a reviewer requests architectural changes, merge conflicts involve unfamiliar files, or reviewers contradict each other. The user explicitly saying stop also always overrides the loop.

Only when all reviewers have approved, all CI checks are green, there are no conflicts, and the user gave explicit merge permission or standing merge authority. Approval alone without green CI is never sufficient.