pr-monitor
Monitor a PR through CI, reviews, and merge conflicts until ready for human review. Use when user says "monitor PR", "watch PR", "wait for CI", or wants automated PR workflow. Creates PR if needed, then monitors Dagger CI, automated review comments, and merge conflicts.
What this skill does
# PR Monitor Skill
Automates the complete PR workflow: create PR, monitor CI/reviews/conflicts, fix issues, and notify when ready.
## Workflow
When invoked:
1. **Create PR** (if not already created)
- Push current branch to remote
- Create PR with `gh pr create`
2. **Monitor Loop** (every 60 seconds)
Check three things and resolve issues found:
### A. Dagger CI Status
- Run `gh pr checks` to see CI status
- If CI is running, wait for completion
- If CI fails, investigate logs with `gh run view <run-id> --log`
- **IMPORTANT**: Errors about "url params" or "GraphQL" are misleading - look for the actual error higher in the logs
- Fix any issues found and push amendments
### B. Review Comments & Approval
- Check for automated Claude Code review comments with `gh pr view --json reviews,reviewDecision`
- Address ALL issues found by automated reviews
- PR is NOT approved until it has a GitHub approval status
- Note: PR may be approved then have changes requested after revisions
### C. Merge Conflicts
- Check if behind main with `git fetch origin main && git merge-base --is-ancestor origin/main HEAD`
- If behind, merge from main and resolve any conflicts that arise
- YOU are responsible for merge conflicts, not the user
3. **Completion Check**
- Verify ALL THREE checks pass simultaneously
- No new automated issues/concerns
- Only then notify user
4. **Notify User**
- Report PR is ready for human review
- Provide PR title and URL
## Commands Reference
### Create/Check PR
```bash
# Push branch
git push -u origin $(git branch --show-current)
# Create PR
gh pr create --fill
# Check if PR exists
gh pr view --json number,url
```
### Monitor CI
```bash
# Check all PR checks
gh pr checks
# Get detailed status
gh pr checks --json name,status,conclusion
# View failed run logs
gh run list --limit 1 --json databaseId,conclusion
gh run view <run-id> --log
```
### Check Reviews
```bash
# Get review status
gh pr view --json reviews,reviewDecision
# List review comments
gh api repos/{owner}/{repo}/pulls/{number}/comments
# Check if approved
gh pr view --json reviewDecision --jq '.reviewDecision'
```
### Handle Merge Conflicts
```bash
# Fetch latest main
git fetch origin main
# Check if behind main
git merge-base --is-ancestor origin/main HEAD && echo "Up to date" || echo "Need to merge"
# Merge from main
git merge origin/main
# After resolving conflicts
git add .
git commit -m "Merge main and resolve conflicts"
git push
```
### Amend and Push
```bash
# Stage changes
git add .
# Amend commit
git commit --amend --no-edit
# Force push
git push --force-with-lease
```
## Important Notes
1. **Misleading CI Errors**: "url params" or "GraphQL" errors from Dagger are usually not the root cause. Scroll up in logs to find the actual failure.
2. **Automated Reviews**: Claude Code automated reviews must ALL be addressed. The PR isn't approved until GitHub shows an approval.
3. **Approval State**: A PR may be approved, then after you make changes, it may have "changes requested" status again. Keep iterating.
4. **Merge Conflicts**: Always resolve these yourself rather than asking the user.
5. **Polling Interval**: Check every 60 seconds to avoid rate limiting while still being responsive.
6. **Final Verification**: Before notifying the user, double-check that:
- CI is green
- PR has GitHub approval
- No merge conflicts with main
- No outstanding review comments
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.