con un clic
kubernetes-debug
Use for Kubernetes Debugging Sessions
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Menú
Use for Kubernetes Debugging Sessions
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
A relentless interview that asks every frontier question at once, round by round. (Sherif's version).
Load when creating a new skill, scaffolding a SKILL.md, adding a reference page to a skill, writing or tuning a skill's description, or restyling/auditing an existing skill. Carries the authoring patterns (progressive disclosure, router, voice, triggering) a skill is shaped with.
Load when planning or about to git commit, branch, push, rebase, resolve a merge conflict, open PR, stack PR, or write/update the description of a Pull Request (PR / stacked diff), respond to review comments, review a PR, or watch/babysit a PR's CI. Carries the user's git conventions and style you are expected to match. Load as early as possible, the moment git or GitHub work is anywhere in the chat's future.
The user's coding and docs conventions and taste. Load FIRST, at the start of any task that touches code or docs.
Use when setting up, shaping, or auditing a project's CI/CD: a build/test/scan pipeline, a release pipeline, or publishing an artifact (container image, binary, bundle) with signing/attestation. Optionally use the skill to transform a repo's CI/CD to the recommended shape, aka (cicd-fy).
/afk, but local-only and conservative.
| name | kubernetes-debug |
| description | Use for Kubernetes Debugging Sessions |
| license | MIT |
| argument-hint | [debug <resource> | investigate <symptom>] |
| metadata | {"author":"sherifabdlnaby","version":"0.1.0"} |
Route first: the debugging procedure lives in a references/ file. Open the matching one before investigating; reading it late means redoing the diagnosis.
Debugging / investigating (why is X Pending / CrashLooping / not ready / reverted / 503ing / not scaling / not provisioning) -> references/debugging.md
evict instead of Pod Deletion for restarts.