Skill

org-ci-health

Quick scan of CI status across all repos in an org, flagging failures and stale workflows

npx claudepluginhub seabbs/skills --plugin org-management

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Scan CI status across repos in an org.

SKILL.md

Similar Skills

ui-ux-pro-max

72.7k

Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.

ui-ux-pro-max

context7-mcp

51.8k

Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.

context7-plugin

competitive-landscape

32.9k

Analyzes competition with Porter's Five Forces, Blue Ocean Strategy, and positioning maps to identify differentiation opportunities and market positioning for startups and pitches.

startup-business-analyst

Stats

Parent Repo Stars0

Parent Repo Forks1

Last CommitFeb 23, 2026

Actions

View Source View Plugin View on GitHub View README

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.

~/.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):

Create a worktree branch
Apply the fix
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.