Can this skill be used for non-Go projects?

No, this specific skill is architected specifically for the Go ecosystem and its unique tooling like gofmt and the Go compiler.

When should I trigger the post-change verification?

This skill should be used every time code is created, modified, or refactored to ensure the changes haven't introduced regressions or style violations.

What Go tools are required for this skill?

The skill utilizes standard Go toolchain commands including go fmt, go build, and go test. It also recommends golangci-lint for comprehensive code analysis.

Does this skill require a Makefile?

While it prioritizes Makefile targets like 'make lint' or 'make test' for project consistency, it gracefully falls back to direct Go commands if a Makefile is not present.

How does it handle pre-existing linting errors?

It uses a specific decision tree: small pre-existing fixes (under 10 lines) are resolved immediately, while larger issues are documented and reported as separate cleanup tasks.

Go Post-Change Verification

Name: Go Post-Change Verification
Author: IvanTorresEdge

byIvanTorresEdge

安全与测试

Enforces a mandatory quality assurance protocol for Go projects through automated formatting, linting, building, and testing sequences.

关于

This skill establishes a rigorous verification workflow for Go developers using Claude, ensuring that every code modification—whether it is a new feature, a bug fix, or a refactor—is technically sound and follows best practices. It guides Claude through a strict sequence of formatting with go fmt, linting with golangci-lint, compilation checks, and test execution. By providing a standardized reporting format and an intelligent decision tree for handling pre-existing technical debt versus new issues, it ensures high-quality contributions while maintaining development velocity.

主要功能

Intelligent exception handling for pre-existing code issues
Standardized verification reporting for clear task completion status
0 GitHub stars
Mandatory 4-step verification sequence (Format, Lint, Build, Test)
Automatic Makefile target detection with native Go command fallbacks
Consistent enforcement of the 10-line rule for minor technical debt fixes

使用场景

Validating new Go function implementations before task completion
Automating multi-step quality checks during complex Go backend development
Ensuring refactored Go code maintains build integrity and test coverage

关于

主要功能

Intelligent exception handling for pre-existing code issues
Standardized verification reporting for clear task completion status
0 GitHub stars
Mandatory 4-step verification sequence (Format, Lint, Build, Test)
Automatic Makefile target detection with native Go command fallbacks
Consistent enforcement of the 10-line rule for minor technical debt fixes

使用场景

Validating new Go function implementations before task completion
Automating multi-step quality checks during complex Go backend development
Ensuring refactored Go code maintains build integrity and test coverage