All authors
Claude Skills by serpro69
github.com/serpro6963 skills0 installs82 views
- Test SkillA test skillVotes: 0GitHub stars: 150
- Golang SecurityA Go security skill for reviewing codeVotes: 0GitHub stars: 150
- Golang TestingGo testing best practicesVotes: 0GitHub stars: 150
- Chain Of VerificationApply 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.Votes: 0GitHub stars: 150
- Dependency HandlingTRIGGER 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.Votes: 0GitHub stars: 150
- DesignTRIGGER when: asked to write or refine a technical design, PRD, specification, implementation plan, or task list, or resume an existing docs/feat/wip feature. Turns ideas and requirements into written design documents, implementation plans, and tasks in docs/feat/wip/ before coding. For conversational exploration without written planning, use /kk:brainstorm.Votes: 0GitHub stars: 150
- Diff SkillCompare 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.Votes: 0GitHub stars: 150
- AfterReviews tool configurations for correctness.Votes: 0GitHub stars: 150
- BeforeReviews tool configurations for correctness.Votes: 0GitHub stars: 150
- DocumentAfter 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.Votes: 0GitHub stars: 150
- ImplementTRIGGER when: user asks to implement, fix, build, or work on something — whether from a docs/feat/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.Votes: 0GitHub stars: 150
- Merge DocsCompare 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.Votes: 0GitHub stars: 150
- Review CodeCode 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.Votes: 0GitHub stars: 150
- Review DesignReview design, implementation, and task documents produced by design. Evaluates document quality, internal consistency, and technical soundness. Use after design completes and before starting implement.Votes: 0GitHub stars: 150
- Review SpecUse 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.Votes: 0GitHub stars: 150
- TestGuidelines 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.Votes: 0GitHub stars: 150
- AlphaAlpha 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.Votes: 0GitHub stars: 150
- BetaBeta 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).Votes: 0GitHub stars: 150
- AfterAn example skill for testing diff-skill evaluation.Votes: 0GitHub stars: 150
- BeforeAn example skill for testing diff-skill evaluation.Votes: 0GitHub stars: 150
- Review ArchitectureReview a written architecture artifact — an ADR (docs/adr/), a broader architecture doc, the architecture section of a design doc, or a domain-reference kit (glossary + traps pages, reviewed as one composite artifact) — against the system it claims to describe. Verifies the EXISTENCE and TOPOLOGY of declared mechanisms (structural boundaries, data ownership, NFR mechanisms, failure isolation, state consistency, evolution/versioning, domain binding) plus decision soundness, reversibility, and ...Votes: 0GitHub stars: 150
- Chain Of VerificationApply 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.Votes: 0GitHub stars: 150
- Dependency HandlingTRIGGER 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.Votes: 0GitHub stars: 150
- DesignTRIGGER when: asked to write or refine a technical design, PRD, specification, implementation plan, or task list, or resume an existing docs/feat/wip feature. Turns ideas and requirements into written design documents, implementation plans, and tasks in docs/feat/wip/ before coding. For conversational exploration without written planning, use $kk:brainstorm.Votes: 0GitHub stars: 150
- Diff SkillCompare 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.Votes: 0GitHub stars: 150
- AfterReviews tool configurations for correctness.Votes: 0GitHub stars: 150
- BeforeReviews tool configurations for correctness.Votes: 0GitHub stars: 150
- AfterAn example skill for testing diff-skill evaluation.Votes: 0GitHub stars: 150
- BeforeAn example skill for testing diff-skill evaluation.Votes: 0GitHub stars: 150
- DocumentAfter 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.Votes: 0GitHub stars: 150
- ImplementTRIGGER when: user asks to implement, fix, build, or work on something — whether from a docs/feat/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.Votes: 0GitHub stars: 150
- Merge DocsCompare 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.Votes: 0GitHub stars: 150
- Review ArchitectureReview a written architecture artifact — an ADR (docs/adr/), a broader architecture doc, the architecture section of a design doc, or a domain-reference kit (glossary + traps pages, reviewed as one composite artifact) — against the system it claims to describe. Verifies the EXISTENCE and TOPOLOGY of declared mechanisms (structural boundaries, data ownership, NFR mechanisms, failure isolation, state consistency, evolution/versioning, domain binding) plus decision soundness, reversibility, and ...Votes: 0GitHub stars: 150
- Review CodeCode 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.Votes: 0GitHub stars: 150
- Review DesignReview design, implementation, and task documents produced by design. Evaluates document quality, internal consistency, and technical soundness. Use after design completes and before starting implement.Votes: 0GitHub stars: 150
- Review SpecUse 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.Votes: 0GitHub stars: 150
- TestGuidelines 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.Votes: 0GitHub stars: 150
- GreetGreet the user by name in their preferred language. Use when the user asks for a greeting or a one-line introduction message.Votes: 0GitHub stars: 150
- ModelProduce or update a domain-reference kit — the durable glossary + divergences/traps pages for a bounded context. Use for domain modelling, information architecture, building a domain glossary or domain model, mapping domain concepts to code (bindings), or surfacing the decidable questions stakeholders must close before design. Runs upstream of feature /kk:design as the first producer of the architecture flow, and emits artifacts /kk:review-architecture verifies. Triggers: "model the domain", ...Votes: 0GitHub stars: 150
- GreetGreet the user by name in their preferred language. Use when the user asks for a greeting or a one-line introduction message.Votes: 0GitHub stars: 150
- ModelProduce or update a domain-reference kit — the durable glossary + divergences/traps pages for a bounded context. Use for domain modelling, information architecture, building a domain glossary or domain model, mapping domain concepts to code (bindings), or surfacing the decidable questions stakeholders must close before design. Runs upstream of feature $kk:design as the first producer of the architecture flow, and emits artifacts $kk:review-architecture verifies. Triggers: "model the domain", ...Votes: 0GitHub stars: 150
- InstructionsTRIGGER when: asked to clarify or improve the explanation in existing local human documentation, such as a guide, design document, or implementation plan. Grounds edits in requirements and source while preserving technical meaning. Not for code, config, generic response brevity, PR drafts, or agent instructions. Explicit instruction or SKILL.md targets receive a /kk:implement suggestion without edits or automatic handoff.Votes: 0GitHub stars: 150
- OriginalGreet the user.Votes: 0GitHub stars: 150
- InstructionsTRIGGER when: asked to clarify or improve the explanation in existing local human documentation or a PR-description draft, including a PR URL or pasted body. Grounds edits in requirements and source while preserving technical meaning. Not for code, config, generic response brevity, or agent instructions. Explicit instruction or SKILL.md targets receive a /kk:implement suggestion without edits or automatic handoff.Votes: 0GitHub stars: 150
- Clarify DocsTRIGGER when: asked to clarify or improve existing documentation, PR drafts or issue descriptions, including URLs and pasted bodies. Saves results locally, grounded in requirements and source while preserving meaning. Not for requests to implement, fix or work on an issue, code, config, generic response brevity, or agent instructions. Explicit instruction or SKILL.md targets receive a /kk:implement suggestion without edits or automatic handoff.Votes: 0GitHub stars: 150
- Clarify DocsTRIGGER when: asked to clarify or improve existing documentation, PR drafts or issue descriptions, including URLs and pasted bodies. Saves results locally, grounded in requirements and source while preserving meaning. Not for requests to implement, fix or work on an issue, code, config, generic response brevity, or agent instructions. Explicit instruction or SKILL.md targets receive a $kk:implement suggestion without edits or automatic handoff.Votes: 0GitHub stars: 150
- Test FilesGreet the user.Votes: 0GitHub stars: 150
- BaselineTRIGGER when: asked to clarify or improve the explanation in existing documentation or a PR-description draft, including a PR URL or pasted body. Saves results locally. Grounds edits in requirements and source while preserving technical meaning. Not for code, config, generic response brevity, or agent instructions. Explicit instruction or SKILL.md targets receive a /kk:implement suggestion without edits or automatic handoff.Votes: 0GitHub stars: 150
- RevisedTRIGGER when: asked to clarify or improve existing documentation, PR drafts or issue descriptions, including URLs and pasted bodies. Saves results locally, grounded in requirements and source while preserving meaning. Not for requests to implement, fix or work on an issue, code, config, generic response brevity, or agent instructions. Explicit instruction or SKILL.md targets receive a /kk:implement suggestion without edits or automatic handoff.Votes: 0GitHub stars: 150
- DesignUse 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/feat/wip/.Votes: 0GitHub stars: 150