Token导航 LogoToken导航TokenDH.com
研究检索执行命令github未标认证来源可访问许可证需确认审计通过

go-usecase去用例

Agent Skill

go-usecase 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

539

周安装

22

GitHub Stars

公开资料未说明

下载量

172
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:go-usecase(去用例)
来源仓库:https://github.com/cristiano-pacheco/ai-tools
仓库路径:skills/go-usecase
安装命令:
npx skills add https://github.com/cristiano-pacheco/ai-tools --skill go-usecase
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/cristiano-pacheco/ai-tools --skill go-usecase

简介

go-usecase 用于查找、检索和筛选相关信息。

  • 适合在 Codex、Claude、Cursor、Gemini CLI 中根据关键词快速定位候选结果。
  • 通过 npx skills add 命令从指定 GitHub 仓库安装并使用。
  • 安装前需确认权限范围、维护状态及是否触发联网或文件操作。
  • go-usecase 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

Go UseCase

Generate use case implementation for Go modular architecture.

When to Use

  • Create business operations with Execute pattern
  • CRUD use cases for any module
  • Operations requiring input validation and error handling
  • Any domain logic orchestrating ports

File Pattern

One file per operation: internal/modules/<module>/usecase/<noun>_<action>_usecase.go

Examples: user_create_usecase.go, product_update_usecase.go, order_cancel_usecase.go

Naming Convention

Given noun User and action Create:

ElementName
Fileuser_create_usecase.go
StructUserCreateUseCase
InputUserCreateInput
OutputUserCreateOutput
ConstructorNewUserCreateUseCase
MethodExecute

Pattern: NounAction + UseCase for the struct. NounAction + Input / Output for DTOs.

Structure

package usecase

import (
	"context"

	"github.com/cristiano-pacheco/bricks/pkg/logger"
	"github.com/cristiano-pacheco/bricks/pkg/validator"
	"github.com/cristiano-pacheco/gomies/internal/modules/<module>/model"
	"github.com/cristiano-pacheco/gomies/internal/modules/<module>/ports"
)

type NounActionInput struct {
	FirstName string `validate:"required,min=3,max=255"`
	LastName  string `validate:"required,min=3,max=255"`
	Password  string `validate:"required,min=8"`
	Email     string `validate:"required,email,max=255"`
}

type NounActionOutput struct {
	FirstName string
	LastName  string
	Email     string
	UserID    uint64
}

type NounActionUseCase struct {
	userRepository ports.UserRepository
	validator      validator.Validator
	logger         logger.Logger
}

func NewNounActionUseCase(
	userRepository ports.UserRepository,
	validator validator.Validator,
	logger logger.Logger,
) *NounActionUseCase {
	return &NounActionUseCase{
		validator: validator,
		logger:    logger,
	}
}

func (uc *NounActionUseCase) Execute(ctx context.Context, input NounActionInput) (NounActionOutput, error) {
	err := uc.validator.Struct(input)
	if err != nil {
		uc.logger.Error("user creation validation failed", logger.Error(err))
		return NounActionOutput{}, err
	}

	userModel := model.UserModel{
		FirstName: input.FirstName,
		LastName:  input.LastName,
		Email:     input.Email,
		Password:  input.Password,
	}

	createdUser, err := uc.userRepository.Create(ctx, userModel)
	if err != nil {
		uc.logger.Error("user creation failed", logger.Error(err))
		return NounActionOutput{}, err
	}

	output := NounActionOutput{
		UserID:    createdUser.ID,
		FirstName: createdUser.FirstName,
		LastName:  createdUser.LastName,
		Email:     createdUser.Email,
	}

	return output, nil
}

Execute Method Flow

  1. Validate input — always first: uc.validator.Struct(input)
  2. Business logic — repository calls, service calls, domain checks
  3. Log every error before returning it
  4. Return typed errors from errs package
  5. Map result to Output struct and return

Input Validation

Define constraints via validate struct tags on the Input struct. Call uc.validator.Struct(input) as the first line inside Execute. Return validation errors directly — the shared validator formats them.

Common tags: required, min=N, max=N, email, oneof=val1 val2 val3

Error Handling

Every error from a repository, service, or external call MUST be logged before returning:

entity, err := uc.entityRepo.FindByID(ctx, input.ID)
if err != nil {
	uc.logger.Error("error finding entity by id", logger.Error(err))
	return EntityGetOutput{}, err
}

For not-found checks where absence is expected (not a terminal error):

entity, err := uc.entityRepo.FindByEmail(ctx, input.Email)
if err != nil && !errors.Is(err, bricserrs.ErrRecordNotFound) {
	uc.logger.Error("error finding entity by email", logger.Error(err))
	return EntityCreateOutput{}, err
}
if entity.ID != 0 {
	return EntityCreateOutput{}, errs.ErrEmailAlreadyInUse
}

Import for bricks errors: bricserrs "github.com/cristiano-pacheco/bricks/errs"

Return typed module errors from errs — never errors.New(...).

Dependencies

Every use case includes these shared dependencies:

  • validator.Validator — input struct validation via tags
  • logger.Logger — error logging

Never inject concrete types for module dependencies.

Fx Wiring

In the module's fx.go, register raw constructors and a single provideDecoratedUseCases function that wraps them all.

Single use case

var Module = fx.Module(
	"<module-name>",
	fx.Provide(
		usecase.NewEntityCreateUseCase,
		provideDecoratedUseCases,
	),
)

type decorateUseCasesIn struct {
	fx.In
	UseCaseDecoratorFactory *ucdecorator.Factory
	EntityCreateUseCase     *usecase.EntityCreateUseCase
}

type decorateUseCasesOut struct {
	fx.Out
	EntityCreateUseCase ucdecorator.UseCase[usecase.EntityCreateInput, usecase.EntityCreateOutput]
}

func provideDecoratedUseCases(in decorateUseCasesIn) decorateUseCasesOut {
	return decorateUseCasesOut{
		EntityCreateUseCase: ucdecorator.Wrap(in.UseCaseDecoratorFactory, in.EntityCreateUseCase),
	}
}

Anti-Patterns

Missing input validation — BAD

func (uc *UserCreateUseCase) Execute(ctx context.Context, input UserCreateInput) (UserCreateOutput, error) {
	// BAD: skipped uc.validator.Struct(input)
	user, err := uc.userRepository.Create(ctx, ...)

Unlogged error — BAD

// BAD
entity, err := uc.entityRepo.FindByID(ctx, input.ID)
if err != nil {
	return EntityGetOutput{}, err
}

// GOOD
entity, err := uc.entityRepo.FindByID(ctx, input.ID)
if err != nil {
	uc.logger.Error("error finding entity by id", logger.Error(err))
	return EntityGetOutput{}, err
}

Raw errors — BAD

// BAD
return UserCreateOutput{}, errors.New("email already in use")

// GOOD
return UserCreateOutput{}, errs.ErrEmailAlreadyInUse

Tracing/metrics inside use case — BAD

// BAD: observability belongs in ucdecorator
ctx, span := trace.Span(ctx, "UserCreateUseCase.Execute")
defer span.End()

Concrete type injection — BAD

// BAD
type UserCreateUseCase struct {
	userRepository *repository.UserRepository
}

// GOOD
type UserCreateUseCase struct {
	userRepository ports.UserRepository
}

Wrong naming — BAD

// BAD: Input/Output not following NounAction pattern
type CreateUserInput struct {}
type CreateUserOutput struct {}

// GOOD
type UserCreateInput struct {}
type UserCreateOutput struct {}

Redundant comments — BAD

// BAD
// Execute executes the user create use case.
func (uc *UserCreateUseCase) Execute(...) {}

// NewUserCreateUseCase creates a new UserCreateUseCase.
func NewUserCreateUseCase(...) *UserCreateUseCase {}

Every error must be logged. Each use case must define its own Input and Output types in its own use case file, and those boundary types must be self-contained. Input/Output MUST NOT embed or reference shared module DTOs/models Input/Output MUST declare all fields explicitly, either directly or via nested structs declared in the same use case file. Input/Output types are private to that use case contract and MUST NOT be reused by other use cases. Shared shapes belong in repository/service/domain layers, not in use case boundary contracts. Input/Output types must not have json tags

Critical Rules

  1. Naming: Struct NounActionUseCase, Input NounActionInput, Output NounActionOutput. No exceptions.
  2. Both Input and Output: Always define both structs, even if empty.
  3. Validate first: uc.validator.Struct(input) is always the first call in Execute.
  4. Log every error: uc.logger.Error(msg, logger.Error(err)) before every error return.
  5. Typed errors: Return errors from module errs package — never errors.New(...).
  6. No tracing/metrics: Observability handled by ucdecorator externally.
  7. Port interfaces: Module deps must be ports.* interfaces.
  8. Single Execute: One public method Execute(ctx context.Context, input Input) (Output, error).
  9. Constructor returns pointer: NewNounActionUseCase(...) returns *NounActionUseCase.
  10. No standalone functions: Logic in Execute or private methods only.
  11. No redundant comments: Do not restate method/constructor names.
  12. Fx decoration: Wrap with ucdecorator.Wrap via fx.In/fx.Out structs.

Anti-pattern: Standalone functions

Standalone functions at the package level are forbidden when a struct with methods exists in the file. They pollute the package namespace, can collide with helpers in other service files, and fragment logic that belongs to the struct.

Workflow

  1. Create usecase/<noun>_<action>_usecase.go
  2. Define Input (with validate tags), Output, struct, constructor, Execute
  3. Add Fx wiring to module's fx.go (constructor + provideDecoratedUseCases)
  4. Run make lint and make nilaway to verify the use case follows all patterns and has no nil pointer risks.

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

36.05%
按下载量换算62

Claude

29.51%
按下载量换算51

Cursor

19.91%
按下载量换算34

Gemini CLI

9.29%
按下载量换算16

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

执行命令

安装流程涉及命令执行,可能通过 npx skills add https://github.com/cristiano-pacheco/ai-tools --skill go-usecase 联网下载 Skill 或依赖。用户安装前应确认命令来源、仓库内容和执行环境。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills