pr-automate
Run as a background subagent after a PR is created or pushed. Acts as a continuous quality gate, posting review findings, watching CI and mergeability, and relaying human feedback back to the main thread. Invoke via the Agent tool with run_in_background true.
What this skill does
# PR Automate Background PR maintenance, feedback relay, and continuous review. Runs alongside the main agent as a quality gate. ## When to use Spawn this skill as a background subagent after either: - A new PR is created (`gh pr create` completes), or - A push lands on a branch with an open PR (`git push` completes) The main agent invokes it via the `Agent` tool with `run_in_background: true` so it can work in parallel without blocking. ## Procedures ### 0. Tag the PR as agent-authored - Run this step only when spawned after a PR was just created (the post-create path). Skip on the post-push path if the PR already carries the notice. - Prepend the following line to the PR body: **This is entirely from an agent so do not review until I have pinged for review as I will do a first pass** - Update the PR via `gh pr edit --body` (or the GraphQL equivalent). - Confirm the notice is in place before moving on. ### 1. Initial review - Run the `review` skill from `dev-workflow`. - Report the full summary of Critical and Important findings back to the main thread. - Post each finding as an inline PR comment via `gh api`. Skip suggestions. - Confirm to the main thread once both reporting and posting are done. ### 2. CI / conflict loop — "the janitor" (30 min) - Every 3 min, check `gh pr checks` and mergeability. - Resolve technical hurdles (CI failures, conflicts) using the `lint` and `test` skills. - Report success or unfixable failures back to the main thread. ### 3. Continuous integration review — "the watcher" - Watch the PR for new commits pushed by the main agent. - When new commits land, run a targeted `review` on the new changes. - Report regressions or new Critical/Important issues back immediately. ### 4. Feedback relay — "the messenger" (up to 4 h) - Poll for new reviews or comments from `seabbs` or `seabbs-bot`. - Report the full content and location of the feedback to the main thread. - Do not fix human feedback; let the main agent implement intent while this skill keeps monitoring resulting commits. - Timing: 10 min intervals for 30 min, then 30 min intervals. ## Rules - Run with `run_in_background: true`. - Act as a continuous quality gate for the main agent, not a replacement. - Keep reports concise but complete. - Use separate Bash calls; do not trigger permission prompts. - Treat `seabbs` and `seabbs-bot` feedback as high priority.
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.