pr-worker
Spawn a Claude worker to address PR feedback, fix CI failures, or continue work on a pull request. Use when a PR needs updates based on review comments or failing checks.
What this skill does
# PR Worker Skill
Spawn a Claude worker to address PR feedback or continue PR work.
## Usage
```
/pr-worker <pr-number>
/pr-worker <pr-number> --review # Address review comments
/pr-worker <pr-number> --ci # Fix CI failures
```
## Examples
```
/pr-worker 123
/pr-worker 123 --review
/pr-worker 123 --ci
```
## Instructions
When the user invokes `/pr-worker`, follow these steps:
### 1. Fetch PR Details
```bash
gh pr view <pr-number> --json number,title,body,headRefName,baseRefName,state,reviewDecision,statusCheckRollup,reviews,comments
```
### 2. Determine Work Type
Based on flags or auto-detect:
- `--review`: Focus on addressing review comments
- `--ci`: Focus on fixing CI failures
- Default: Analyze PR state and decide
### 3. Get Existing Worktree or Create One
Check if worktree for this branch already exists:
```bash
git worktree list | grep <headRefName>
```
If not, create one:
```bash
BRANCH="<headRefName>"
WORKTREE_PATH="../artemis-pr-<number>"
git worktree add "$WORKTREE_PATH" "$BRANCH"
```
### 4. Build Task Prompt
#### For Review Comments (`--review`):
```bash
gh pr view <number> --comments
gh api repos/{owner}/{repo}/pulls/<number>/comments
```
Build prompt:
```
You are addressing review feedback on PR #<number>: <title>
## Review Comments to Address
<list of unresolved comments with file paths and line numbers>
## Your Task
1. Address each review comment
2. Make the requested changes
3. Commit with message: "fix: address PR review feedback"
4. Do NOT push - the orchestrator will handle that
```
#### For CI Failures (`--ci`):
```bash
gh pr checks <number>
gh run view <failed-run-id> --log-failed
```
Build prompt:
```
You are fixing CI failures on PR #<number>: <title>
## Failed Checks
<list of failed checks with error logs>
## Your Task
1. Analyze the CI failure logs
2. Fix the issues causing failures
3. Commit with message: "fix: resolve CI failures"
4. Do NOT push - the orchestrator will handle that
```
### 5. Spawn Worker
```bash
cd "$WORKTREE_PATH" && claude --print --dangerously-skip-permissions "$PROMPT"
```
### 6. Report and Push
After worker completes:
1. Show commits made
2. Offer to push: `git push origin <branch>`
3. Show updated PR status
```bash
git push origin <branch>
gh pr checks <number> # Verify CI is running
```
## Notes
- PR workers reuse existing worktrees if the branch exists
- Worker should NOT force push or amend existing commits
- Always show diff before pushing
- CI worker may need multiple iterations if fixes introduce new failures
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.