org-ci-health
Quick scan of CI status across all repos in an org, flagging failures and stale workflows
What this skill does
# CI Health Check
Scan CI status across repos in an org.
Run from `~/code/{org}/` or pass the org name as an argument.
## Helper script
A pre-built script at `~/.claude/scripts/org-ci-health.sh` collects all CI data in one pass.
Run it first to avoid spending tokens on individual `gh` calls.
```bash
~/.claude/scripts/org-ci-health.sh <org-name> > /tmp/org-ci-health.json
```
If the script is missing or not executable, flag this to the user and stop.
The script outputs a JSON array with per-repo entries containing:
- `repo`, `gh_org`, `has_workflows`
- `recent_runs` (last 5 CI runs on main with status/conclusion)
- `actions_used` (list of `uses:` action references from workflows)
## Phase 1: Analyse script output
Parse the JSON and flag:
- **Failing**: latest main CI conclusion is not "success"
- **Stale**: no CI run in 30+ days
- **No CI**: `has_workflows` is false
## Phase 2: Check workflow versions
From `actions_used`, flag:
- Actions using deprecated versions (e.g. `actions/checkout@v3` when `v4` exists)
- Actions pinned to branches instead of tags
- Outdated `actions/setup-r` or `julia-actions/setup-julia`
## Phase 3: Check for common issues
- Workflows using deprecated `set-output` or `save-state` commands
- Missing `permissions:` blocks
- Workflows that run on `push` to all branches (should be limited)
- R packages missing `R-CMD-check` workflow
- Julia packages missing CI workflow
## Phase 4: Report
Present a dashboard:
| Repo | Main CI | Last run | Actions up to date | Issues |
|---|---|---|---|---|
Then list specific issues grouped by repo.
## Phase 5: Fix (with confirmation)
For fixable issues (action version bumps, workflow updates):
1. Create a worktree branch
2. Apply the fix
3. Create a PR
Use a team if more than 3 repos need fixes.
## Auto-Exit When Standalone
**IMPORTANT**: If this command is being run as a standalone request, automatically exit after completing all phases successfully.
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.