From kata-flight
Use to verify a Kata Flight setup. Read-only health check for the .kata-flight seam, marker vars, engine layout, context root, optional RDR binding, and skill links. Trigger for diagnose Kata Flight, check Kata Flight setup, $kata-flight-doctor, or /kata-flight-doctor.
How this skill is triggered — by the user, by Claude, or both
Slash command
/kata-flight:kata-flight-doctor (none - run from any consumer repo/worktree)(none - run from any consumer repo/worktree)The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Read-only health check for a consumer repo bound by `kata-flight-init`.
Read-only health check for a consumer repo bound by kata-flight-init.
It writes nothing and keeps running after failures so the report shows every
broken invariant plus the one repair command.
Run the bundled script file beside this SKILL.md; do not paste its body:
GC=$(git rev-parse --git-common-dir 2>/dev/null) && GC=$(cd "$GC" && pwd -P)
WS=$(dirname "$(dirname "$GC")")
for H in "$KATA_FLIGHT_HOME" "$CLAUDE_PLUGIN_ROOT" "$CODEX_PLUGIN_ROOT" "$WS/kata-flight"; do [ -f "$H/skills/kata-flight-doctor/doctor.sh" ] && { sh "$H/skills/kata-flight-doctor/doctor.sh"; break; }; done
Under Codex, if the environment vars are unset, run the doctor.sh that sits
beside this filesystem-backed skill.
Print the script stdout verbatim inside a fenced block. Do not reformat it. If a line says FAIL, surface its fix as-is.
Next: /kata-flow-ops, /kata-flight <selector>, or
/kata-flight-init only when rebinding deliberately./kata-flight-init, then re-run
/kata-flight-doctor.npx claudepluginhub cwensel/kata-flight --plugin kata-flightCreates, edits, and verifies skills using a test-driven development approach with pressure scenarios and subagents.