safe-ship
Full shipping workflow: analyze, review, CI, merge, and track deferred issues
What this skill does
Complete the full safe shipping workflow for the current changes.
> **jj workspace note:** You may be in a non-default jj workspace with no `.git` directory. If `gh` commands fail, set `GIT_DIR` to point to the default workspace: `GIT_DIR=/path/to/default/.git gh ...`
**Prerequisites:** This workflow uses `/analyze`, `/push-pr`, `/code-review-jj:code-review`, and `/watch-ci-merge`. Ensure these are available.
## Phase 1: Pre-Push Analysis
1. Check for changes: `jj status` — if no changes, report and stop
2. **Run `/analyze`** to check type safety, bugs, and code simplification
3. **Address all critical and high severity issues** found
4. **Re-run `/analyze`** (max 3 iterations)
5. If critical/high issues persist after 3 rounds, stop and ask for guidance
6. Track any medium and low priority suggestions for later
## Phase 2: Push and Create PR
1. Run `/push-pr` to push changes and create a pull request
2. If PR already exists, just push the updated changes
## Phase 3: Code Review
1. **Run `/code-review-jj:code-review`** on the PR
2. Also fetch Copilot/bot review comments: `gh api repos/{owner}/{repo}/pulls/{number}/comments`
3. **Address all critical and high severity issues** from either source
4. **Re-run code review** (max 3 iterations)
5. If critical/high issues persist after 3 rounds, stop and ask for guidance
6. Track any medium and low priority suggestions for later
## Phase 4: CI and Merge
1. **Run `/watch-ci-merge`** to monitor CI, fix failures, and merge
2. This handles: CI monitoring, failure fixing, rebasing, and merging
3. If blocked, `/watch-ci-merge` will stop and report
## Phase 5: Track Deferred Issues
**Only if there are deferred items**, create a GitHub issue after merging:
```bash
gh issue create --title "Follow-up: [brief description] cleanup" --body "..."
```
The issue body should include:
- Source of each suggestion (analyze, code-reviewer, Copilot)
- Link to the original PR comment if applicable (e.g., `https://github.com/{owner}/{repo}/pull/{number}#discussion_r{id}`)
- File and line number where applicable
- The specific suggestion or improvement
- Priority level (medium/low)
---
**Important:**
- Do NOT skip the analyze loop — quality gates matter
- Do NOT merge with unaddressed critical/high issues
- DO track all deferred items — nothing should be forgotten
- If blocked at any phase, report progress and stop
**Done when:** PR is merged and any deferred issues are tracked.
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.