ship
Ship a PR end-to-end: local verify (build, test, lint), push, create or update PR, watch CI to green, address review bot feedback, merge with auto-delete. NEVER uses --admin merge. Triggers: 'ship', 'ship it', 'push and merge', 'land this PR'. SKIP if user just wants to open a PR without merging — use `create-pr` instead.
What this skill does
# Ship Ship a PR: verify build/tests/lint, push, create PR, watch CI, and merge. ## Usage ``` $ship [--no-merge] ``` **Options:** - `--no-merge`: Skip the merge step (just push and watch CI) ## Prerequisites - GitHub CLI (`gh`) installed and authenticated - Changes committed on a feature branch (not `main`/`master`) ## Workflow ### Phase 1: Pre-Flight Verification All must pass before pushing: ```bash go build ./... go test ./... golangci-lint run # if available ``` If any step fails, fix the issue and re-run before continuing. ### Phase 2: Push ```bash CURRENT_BRANCH=$(git branch --show-current) git push -u origin "$CURRENT_BRANCH" ``` ### Phase 3: Create or Find PR Check if a PR already exists for this branch: ```bash PR_URL=$(gh pr view --json url --jq '.url' 2>/dev/null) ``` If no PR exists, create one using the `$create-pr` workflow (or directly with `gh pr create`). ### Phase 4: Watch CI Monitor CI checks until they all pass: ```bash gh pr checks --watch ``` If "no checks reported", wait 10 seconds and retry up to 3 times: ```bash for i in 1 2 3; do sleep 10 && gh pr checks --watch && break; done ``` If checks fail: 1. Get failure details: `gh pr checks --json name,state,description` 2. Analyze and fix the failing check 3. Commit and push the fix 4. Re-run `gh pr checks --watch` ### Phase 5: Merge (unless `--no-merge`) Before merging, verify: 1. All CI checks pass 2. All required reviews are approved ```bash gh pr merge --auto --squash ``` If merge is blocked by required reviews, inform the user and stop. ### Phase 6: Report Display the final PR URL and merge status. ## Completion Criteria 1. Build, tests, and lint all pass 2. Changes pushed to remote 3. PR created (or existing PR found) 4. CI checks pass 5. PR merged (unless `--no-merge` was specified)
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.