Runs build, test, lint, and documentation checks for the clawker Go repository.
npx skills add https://github.com/schmitthub/clawker --skill dev-checks-schmitthub
Please help me install this Agent Skill. Skill: dev-checks Source: https://github.com/schmitthub/clawker/tree/main/.agents/skills/dev-checks Command: npx skills add https://github.com/schmitthub/clawker --skill dev-checks-schmitthub
go test ./... when CLAWKER_AGENT is set. - Completion Checklists: Provides ordered verification steps for code changes, documentation updates, and agent instruction changes, including regression-test-first discipline and pre-commit hook review. - Version Pinning Rules: Enforces exact-version and SHA pinning for Docker images, CI actions, pre-commit hooks, and Go tools. - Use Case: After fixing a bug in the storage package, follow the checklist to add a failing regression test, run go test ./internal/storage/... -count=1, then make test and golangci-lint run before committing. ## Quick Start Ask the agent to run the appropriate dev-checks build and test commands for the clawker repository after making a code change.High-intent search queries and answers about installing and using this skill.
Run `make test` for the unit suite without Docker, or target specific packages with `go test ./internal/storage/... -count=1`. Use `make test-ci` for race checks, uncached results, and coverage.
Run `go build -o bin/clawker ./cmd/clawker` to build the CLI with existing embeds. Only run `make clawker` when embed binaries are missing, since it is slow and fills build caches.
The e2e suite tears down the host control plane, so running `go test ./...` inside an agent container is destructive. Use `make test` or explicit unit package paths instead, and report host checks as pending.
Regenerate mocks with `go generate ./...` from the owning package, since mocks use moq via `//go:generate` and must never be hand-edited. Generate docs with `go run ./cmd/gen-docs --doc-path docs --markdown --website --schemas`, then verify with `make docs-check`.
All external dependencies must be pinned to exact versions with integrity verification: SHA256 digests for Docker base images and container images, SHA commit hashes for CI actions and pre-commit hooks, and exact versions for Go tool installs. Never use `@latest` or floating tags.
LuigiAPCPereiraAutomates Go code linting with golangci-lint, reporting style, correctness, and performance issues.
marin-communityAutomates linting, committing, PR creation, and monitoring for GitHub branches.
growilabsGuide test authors to verify observable behavior instead of internal implementation details.
mporentaFormat, vet, build, and test Go code locally before Docker builds.