Menu
Health check across all 14 ecosystem repos — uncommitted changes, test status, remote sync
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | ecosystem-status |
| description | Health check across all 14 ecosystem repos — uncommitted changes, test status, remote sync |
| user-invocable | true |
| disable-model-invocation | true |
| allowed-tools | Bash |
Scan all ecosystem repos and report their health. This is a read-only diagnostic.
Note: bash ecosystem.sh status does the same thing faster from the hub. Use this skill when you want the AI to interpret and summarize the results.
All paths relative to C:\Users\pon00\Projects\:
Run these checks in parallel where possible:
git status --short — count uncommitted changesgit log --oneline @{upstream}..HEAD 2>/dev/null — commits not pushedgit branch --show-currentDo NOT run tests here (use the ecosystem-test-runner agent for that).
Display a table:
Repo Branch Uncommitted Unpushed
forensic-accounting-toolkit master 0 0
kr-forensic-finance master 2 0
...
Flag any repo with uncommitted changes or unpushed commits with a warning marker.
End with a one-line summary: "X repos clean, Y need attention."
Scan all ecosystem repos for convention deviations. Reports findings; does not fix anything. Use proactively after cross-repo changes.
Validates pipeline parquet outputs for schema compliance, null rates, row count baselines, and freshness. Use after pipeline runs or when triage shows data quality concerns. Fast and read-only (uses haiku).
Run tests across all ecosystem repos and report pass/fail summary. Use when the user wants to verify the ecosystem is healthy or after cross-repo changes.
Runs the krff-shell ETL pipeline with pre/post validation. Use when data needs refreshing, after dependency updates, or when triage shows stale parquets. Reads CLAUDE.md before running.
Research across sibling repos to gather context for cross-project tasks. Use when working in one repo and needing to understand how another repo works, what it exports, or how data flows between them.
Show all open work (board + backlog) with dependency-aware execution order