
from agentclash14
Run lightweight Go-specific checks (detect go.mod, run tests) after commits when Go code is present to catch regressions early.
This skill detects whether a repository contains Go code (go.mod or *.go files) and, when appropriate, runs lightweight Go hygiene checks such as go test ./.... It is designed to run after commits to avoid failing workflows in repos that are documentation-only or lack Go tools installed.
Use this skill in CI or post-commit hooks for repositories that sometimes contain Go components or mixed-language codebases. Trigger it on push/commit events to catch test failures and basic integration problems only when Go files or a module are present.
go test ./...; otherwise skip without marking failure.Agents or CI tooling that can run shell commands and inspect the repo filesystem (GitHub Actions, local CI agents, automation agents with shell access).
Simple Go hygiene check skill that detects go.mod and *.go files, then runs go test ./... if both exist. No bundled scripts — just a bare SKILL.md with 4 bullet points. Instructions are clear but minimal, with no error handling guidance or detailed steps. Useful concept for Go developers in agent workflows but very narrow scope.
Bare-bones skill with no scripts. The SKILL.md is more of a prompt hint than a complete skill definition. No security concerns whatsoever — just detects files and optionally runs go test.