Menü
Switch working context to a specific ecosystem repo
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
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
| name | work |
| description | Switch working context to a specific ecosystem repo |
| user-invocable | true |
| disable-model-invocation | true |
| allowed-tools | Bash, Read, Grep, Glob |
Switch to a specific repo and load its context so the human can immediately give instructions.
The argument $ARGUMENTS is the repo name (e.g., kr-beneish, kr-derivatives, jfia-forensic).
Resolve the path: The repo lives at C:\Users\pon00\Projects/$ARGUMENTS/. If the directory doesn't exist, list available repos and ask the user to pick one.
cd to the repo:
cd /c/Users/pon00/Projects/$ARGUMENTS
Read CLAUDE.md in the repo root to load project context.
3b. Show Known Gaps. Extract the ## Known Gaps table from CLAUDE.md (if present) and display it. Highlight any Unblocked items that relate to the current task or repo area.
Show git status: git status --short — any uncommitted changes.
Show recent commits: git log --oneline -5 — what happened last.
Run tests (if the project has tests):
pytest tests/ -vuv run pytest tests/ -vuv run pytest tests/ -vuv run pytest tests/ -vuv run pytest tests/ -vuv run pytest tests/ -vuv run pytest tests/ -vuv run pytest tests/ -vuv run pytest tests/ -vuv run pytest tests/ -vuv run pytest tests/ -vSummarize in 2-3 lines: project purpose, current state, anything needing attention.