Claude Skills by sherifabdlnaby

Act autonomously while I'm away.

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 SBOM, or signing/attestation. Optionally use the skill to transform a repo's CI/CD to the recommended shape (the cicd-fy mode).

The user's coding and docs conventions and taste. Load FIRST, at the start of any task that touches code or docs.

Act fast, keep me in the zone.

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.

A relentless interview to sharpen a plan or design.

Use for Kubernetes Debugging Sessions

Use when working with mise (mise-en-place) or planning to update mise.toml. If the project use mise consult it even for one-line edits to mise.toml/hk.pkl, hooks, or CI tool setup, as it has the practices and security defaults you'd otherwise skip. Trigger on the intent even when the user never says "mise" (e.g. "update/pin the node version", "set up pre-commit") as long as project already use mise. Don't load for routine mise *use* (run/install/trust) that isn't changing config. Optionally u...

Gate the work behind a local reviewer panel.

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.

/afk, but local-only and conservative.

Ask your questions now, then go /afk.

/afk, max non-destructive autonomy.

Watch a PR's CI/reviews and respond as they land.

Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

Help the user understand the current topic visually with concise diagrams, code-shape sketches, and focused HTML artifacts.

Stop. That last message did not land: re-pitch it.