Claude Skills by serpro69

Alpha links a shared instruction directly, delegates to a peer skill, and spawns a review agent. Together these exercise the markdown-link, symlink (via the sibling `shared-common-helper.md`), skill-invocation, and agent-delegation edges. See [profile detection](../_shared/profile-detection.md) for the profile list. When a deeper pass is warranted, delegate to /kk:beta.

Beta reaches shared resources through the plugin-root variable, which exercises the template-ref (concrete suffix) and parameterized-nav (`<name>` expansion) edges. Its dangling link is the fixture's intentional broken edge. The reviewer agent lives at `${CLAUDE_PLUGIN_ROOT}/agents/example-reviewer.md`. Phase guidance is at `${CLAUDE_PLUGIN_ROOT}/profiles/<name>/review-code/index.md`. Further detail lives in [missing notes](./does-not-exist.md).

A test skill

A Go security skill for reviewing code

Go testing best practices

Apply Chain-of-Verification (CoVe) prompting to improve response accuracy through self-verification. Use when complex questions require fact-checking, technical accuracy, or multi-step reasoning.

TRIGGER when: adding or upgrading any dependency — library, SDK, framework, API, IaC API version (K8s/Terraform/Helm), CRD, or container image. Use BEFORE writing the call. Forces context7/capy lookup instead of guessing.

Use in pre-implementation (idea-to-design) stages to understand spec/requirements and create a correct implementation plan before writing actual code. Turns ideas into a fully-formed PRD/design/specification and implementation-plan. Creates design docs and task lists in docs/wip/.

Compare two versions of a skill's instructions to detect degradations and complexity increases. TRIGGER when: user asks to diff, compare, or review changes to a skill's markdown instructions. Asymmetric check — only regressions count. Additions, clarifications, and strengthenings are not degradations. Compares HEAD → working tree by default. Walks the full reachable file set from SKILL.md via markdown links. Produces a report file under docs/reviews/diff-skill/ and an inline summary.

Reviews tool configurations for correctness.

Reviews tool configurations for correctness.

After implementing a new feature or fixing a bug, make sure to document the changes. Use when writing documentation, after finishing the implementation phase for a feature or a bug-fix.

TRIGGER when: user asks to implement, fix, build, or work on something — whether from a docs/wip plan OR a standalone task (bug fix, GitHub issue, one-off change). Examples: "work on task 1", "fix this bug", "implement feature X from the issue". Provides structured execution with profile detection, dependency handling, review checkpoints.

Compare and merge two design docs for the same feature into a single source of truth. Use when you have competing or complementary design/implementation docs (e.g. from separate design runs) that need reconciling into one unified document.

Code review of current git changes with an expert senior-engineer lens. Detects SOLID violations, security risks, and proposes actionable improvements. Use when performing code reviews.

Review design, implementation, and task documents produced by design. Evaluates document quality, internal consistency, and technical soundness. Use after design completes and before starting implement.

Use after implementing tasks or mid-feature to verify code matches design docs and ensure they are in sync. Detects spec deviations, missing implementations, doc inconsistencies, and outdated docs in design and implementation documentation.

Guidelines describing how to test the code. Use whenever writing new or updating existing code, for example after implementing a new feature or fixing a bug.

Apply Chain-of-Verification (CoVe) prompting to improve response accuracy through self-verification. Use for complex questions requiring fact-checking, technical accuracy, or multi-step reasoning.

Use this task to ensure you follow development best practices during development and implementation.

Implement a feature using the written implementation plan. Use when you have a fully-formed written implementation plan to execute in a separate session with review checkpoints

**Goal: Before starting the implementation, make sure you understand the requirements and implementation plan.**

1. Always try to use latest versions for dependencies. 2. If you are not sure, **do not make assumptions about how external dependencies work**. Always consult documentation. 3. Before trying alternative methods, always try to **use context7 MCP to lookup documentation for external dependencies** like libraries, SDKs, APIs and other external frameworks, tools, etc. - **IMPORTANT! Always make sure that documentation version is the same as declared dependency version itself.** - Only rever

After implementing a new feature or fixing a bug, make sure to document the changes. Use after finishing the implementation phase for a feature or a bug-fix

Guidelines describing how to test the code. Use whenever writing new or updating existing code, for example after implementing a new feature or fixing a bug.