anthony-spruyt

This skill should be used when the user asks "how does hookify work", "hookify help", "what is hookify", "how to create hookify rules", "what commands does hookify have", or needs an overview of the hookify plugin system.

This skill should be used when the user asks to "create a hookify rule", "hookify this behavior", "prevent this from happening again", "analyze conversation for unwanted behaviors", or invokes /hookify with or without arguments.

This skill should be used when the user asks to "list hookify rules", "show my hooks", "what hookify rules are configured", "show active rules", or invokes /hookify:list.

This skill should be used when the user asks to "create a hookify rule", "write a hook rule", "configure hookify", "add a hookify rule", "hookify rule syntax", or needs guidance on hookify rule file format, frontmatter fields, and regex patterns.

This skill should be used when the user asks to "enable a hookify rule", "disable a hookify rule", "toggle hookify rules", or "configure hookify rules interactively".

Use when the user asks to "upgrade Kubernetes", "upgrade k8s", "update Kubernetes version", "bump Kubernetes version", mentions a target version like "upgrade to 1.35.1", or when Renovate updates kubernetesVersion in talconfig.yaml. Not for Talos OS upgrades (use talos-upgrade agent).

Architectural and technical review of a design spec. Spawns a subagent reviewer that verifies spec claims against live cluster state and deployed manifests, checks library/framework docs via Context7, and produces severity-ranked findings. Use when iterating on spec quality before implementation planning.

Use when querying Kubernetes pod logs from VictoriaLogs, especially for deleted/completed pods whose logs are no longer available via kubectl. Triggers on "check logs", "pod logs", "victoria logs", "vlogs", or when investigating a dead pod's output.

Use when creating new agents, editing existing agent system prompts, optimizing agent token efficiency, or maintaining agent quality. Applies when agent is too long, not performing well, overtriggering, or when reviewing agent files in .claude/agents/. Does not apply to skills, hooks, commands, or slash commands.

Codebase health scanner and technical debt tracker. Use when the user asks about code quality, technical debt, dead code, large files, god classes, duplicate functions, code smells, naming issues, import cycles, or coupling problems. Also use when asked for a health score, what to fix next, or to create a cleanup plan. Supports 29 languages.

Use when a PR or branch needs automated review and fixing, when the user says "review and fix", "clean up this PR", "fix PR issues", or wants to iterate a PR to passing state

Create a new MegaLinter flavor image configuration