shepherd

Polls open pull requests and merge requests to triage review comments and fix CI failures.

1|Updated Jul 6, 2026
One-click install
npx skills add https://github.com/citytexi/team-yg-pesonal-agent --skill shepherd-citytexi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: shepherd
Source: https://github.com/citytexi/team-yg-pesonal-agent/tree/main/.claude/skills/shepherd
Command: npx skills add https://github.com/citytexi/team-yg-pesonal-agent --skill shepherd-citytexi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Open pull requests and merge requests often stall waiting on review feedback or failing CI checks, forcing developers to repeatedly check status, interpret comments, and push small fixes by hand. This Skill automates that monitoring loop so PRs keep moving without manual babysitting. ## Core Features & Use Cases - Continuous PR/MR polling: Detects GitHub vs GitLab via the git remote and uses gh or glab to list open PRs, read comments, and check CI status on a configurable interval. - Comment triage and batched fixes: Classifies review comments (approvals, change requests, nits, questions), fixes all actionable issues locally, then pushes once with an [autofix] prefix before resolving threads. - CI failure workflow: Reads failing job logs, applies obvious fixes (lint, formatting, simple test breakage), retries flaky jobs, and escalates ambiguous failures to the user instead of guessing. - Use Case: You open three PRs before lunch and ask the agent to shepherd them; it watches for reviewer comments, fixes a lint error that broke CI, pushes the fix, and notifies you when everything is green and ready to merge. ## Quick Start Shepherd my open pull requests and keep them moving until they are merged or need my input.

Frequently Asked Questions about shepherd

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically monitor open pull requests for review feedback?▼

Use a polling loop that lists open PRs with gh or glab, checks for new comments since the last poll, triages each comment by type, and fixes actionable issues locally. Push all fixes in a single commit rather than one push per comment.

How to fix failing CI checks on a GitHub pull request automatically?▼

Check CI status with gh pr checks, retrieve failing logs with gh run view --log-failed, and diagnose the root cause. Apply fixes only when they are obvious, such as lint or formatting errors, and push with a clear ci: fix message.

Does this work with GitLab merge requests as well as GitHub PRs?▼

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

When should automated PR monitoring stop and hand back to a human?▼

Stop when a CI failure repeats across three cycles, a reviewer requests architectural changes, merge conflicts involve unfamiliar files, or the user says to stop. Automated fixes should never guess at ambiguous test failures.

Why should review threads only be resolved after pushing fixes?▼

Resolving threads before pushing marks feedback as addressed when the fix only exists locally. If the push fails or CI rejects the change, reviewers are misled about the PR's actual state.