go-development

Run Makefile targets to lint, format, build, and test Go projects.

126|41|Updated Aug 4, 2018
One-click install
npx skills add https://github.com/hiromaily/go-crypto-wallet --skill go-development-hiromaily
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: go-development
Source: https://github.com/hiromaily/go-crypto-wallet/tree/main/.claude/skills/go-development
Command: npx skills add https://github.com/hiromaily/go-crypto-wallet --skill go-development-hiromaily

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Go development workflow verification and self-review are automated to reduce repetitive checks and improve code quality.

Core Features & Use Cases

  • Verification automation: Run linting, formatting, building, and testing as part of code changes.
  • Self-review guidance: Enforce a checklist for domain logic, error handling, and avoiding sensitive data leakage.
  • Consistent workflow: Aligns with the existing go development rules and git-workflow for branches and PRs.

Quick Start

After editing internal/, pkg/, or cmd/ files, run the standard Makefile targets: go-lint, tidy, check-build, and gotest to verify code quality and tests.

Frequently Asked Questions about go-development

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Go development workflow verification for linting, building, and testing?

Automate Go development workflow verification by running standard Makefile targets: go-lint for linting, tidy for formatting, check-build for building, and gotest for testing after editing internal/, pkg/, or cmd/ files.

What is the best way to self-review Go code before creating a pull request?

Self-review Go code by enforcing a checklist covering domain logic, error handling, and sensitive data leakage prevention, aligning with rules in .claude/rules/go.md and git-workflow for branch management and PR preparation.

Does this Go workflow verification require specific project directory structures?

Go workflow verification targets Go projects specifically within internal/, pkg/, and cmd/ directories, coordinating linting, formatting, building, and testing tasks based on those file paths.

Can I use Makefile targets to coordinate Go linting and formatting tasks?

Use Makefile targets go-lint and tidy to coordinate Go linting and formatting tasks, ensuring code quality and consistency as part of the automated development workflow verification process.

Why does my Go build fail during workflow verification despite passing linting?

Go build failures during workflow verification may occur if the check-build Makefile target detects compilation issues independent of linting, requiring both tidy formatting and successful check-build completion.

What do I need to set up before automating Go code workflow and self-review?

Set up requires a Makefile with go-lint, tidy, check-build, and gotest targets, Go source files in internal/, pkg/, or cmd/ directories, and .claude/rules/go.md guidance for rule alignment.