address-pr
Mid-review entry point: fetch PR comments and CI failures, address them, validate, push. Use when jumping into an existing PR. /dev handles this automatically.
What this skill does
# Address PR Feedback For when you jump into a session with an existing PR that needs attention. Fetches comments and CI failures, addresses them, validates, and pushes. `/dev` does this automatically in its review loop. ## Commit Discipline **Commit and push after every logical fix.** Don't batch all review fixes into one commit. Formatting/lint fixes from dev_checks get their own commit. ## Workflow ### 1. Verify Worktree Run `pwd`. Must contain `.claude/worktrees/`. If not: STOP with error. ### 2. Identify the PR ```bash gh pr view --json number,url,title ``` If no PR exists for this branch, tell the user and stop. ### 3. Gather All Feedback **Review comments:** ```bash gh repo view --json nameWithOwner --jq .nameWithOwner gh pr view <number> --json reviews --jq '.reviews[] | select(.state != "APPROVED") | "\(.author.login) (\(.state)): \(.body)"' gh api repos/<owner>/<repo>/pulls/<number>/comments --jq '.[] | "\(.path):\(.line // .original_line) — \(.user.login): \(.body)"' ``` **CI status:** ```bash gh pr checks <number> ``` If checks failed, fetch logs: ```bash gh run view <run_id> --log-failed ``` Present everything clearly — comments and failures together. ### 4. Address Feedback Work through each item: - **CI failures**: diagnose, fix, run tests locally to confirm, **commit and push** the fix - **Code review — substantive**: make changes, run tests, **commit and push** each logical fix separately - **Code review — questions/style**: ask the user how to respond ### 5. Validate Run full local validation: 1. Unit tests: `uv run pytest tests/unit_tests/ -v` 2. Dev checks: `"$(git rev-parse --show-toplevel)/scripts/dev_checks.sh"` If dev_checks fixes formatting/lint, **commit and push** those separately (`style: fix lint/formatting`). ### 6. Final Check Run `git status` to verify nothing is uncommitted. Everything should already be pushed from step 4. ### 7. Report ```bash gh pr view <number> --json reviewDecision,mergeStateStatus ``` Report: - What changed (list of commits pushed) - Which comments were addressed - Whether the PR is now approved / ready to merge - Any items still needing user input The human decides when to merge.
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.