Go Local Health logo

Go Local Health

Organization
instructa
go-local-health

Run local Go health checks (tests, coverage, lint) in Go repositories that contain go.mod/go.sum. Use when the user asks to run or interpret local Go test/coverage/lint workflows using tools like lazygotest, gocovsh, tparse, and golangci-lint. Do not use for Rust or non-Go projects.

Overview

Publisherinstructa
Repositoryagent-skills
Skill namego-local-health
Stars
141
Forks
16
Bundled files
1
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by instructa on GitHub. Read the source before you install it.

Installation

Install the Go Local Health AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/instructa/agent-skills.git /tmp/agent-skills
mkdir -p .claude/skills
cp -r /tmp/agent-skills/skills/go/go-local-health .claude/skills/go-local-health
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Go Local Health in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Go Local Health on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Go Local Health is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Go Local Health

Overview

Provide a consistent, repeatable local workflow for Go test, coverage, and lint checks. Use this to run fast snapshots, interactive test loops, and coverage inspection without re-deriving commands.

Guardrails (language + tooling)

  • Confirm go.mod exists in the repo root before running anything. If missing, stop and ask.
  • Run commands from the repo root so module settings and tooling config are discovered.
  • Respect the repo’s Go toolchain configuration (go.mod + toolchain).
  • Prefer repo-pinned tool versions (e.g., tools.go or go.mod tool directives). If tools are missing and no pins exist, ask before installing or adding pins.
  • Required tools vary by mode:
    • Quick Snapshot: go, tparse, golangci-lint
    • Interactive Test Loop: lazygotest
    • Coverage Explorer: gocovsh If any required tool is missing, ask to install rather than using substitutes.
  • All automated runs must be non-interactive. Only launch TUIs when the user explicitly requests them.

Workflow Decision Tree

  • Use Quick Snapshot when you want a fast read on tests + coverage + lint.
  • Use Interactive Test Loop when you are actively iterating on tests.
  • Use Coverage Explorer when you need to inspect coverage hotspots in detail.
  • If the repo is large, ask whether to scope to a package path before running full ./....

Quick Snapshot (tests + coverage + lint)

Preferred (scripted, deterministic):

~/.codex/skills/go-local-health/scripts/go-local-health --scope ./...

Manual fallback:

  1. Run tests with coverage and a one-screen summary:
go test -cover -json ./... | tparse
  1. Run lint with the repo’s configuration:
golangci-lint run ./...

If a narrower scope is requested, replace ./... with the specific package path.

Interactive Test Loop (lazygotest)

  • Launch from the repo root:
lazygotest
  • Use the UI to filter packages and re-run tests while editing code.

Coverage Explorer (gocovsh)

  • Launch from the repo root:
gocovsh
  • If a cover.out is required or preferred, generate it first:
go test -coverprofile=cover.out ./...

Reporting Back to the User

  • Summarize failing packages, error types, and coverage gaps.
  • If lint fails, report the top categories (not every line) and ask whether to fix now.
  • If coverage is low, identify the worst packages and suggest next steps only if asked.

Non-Goals

  • Do not run in non-Go repos.
  • Do not swap in other tools or skip required checks.
  • Do not change CI configuration or code unless the user asks.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Go Local Health AI skill do?

Run local Go health checks (tests, coverage, lint) in Go repositories that contain go.mod/go.sum. Use when the user asks to run or interpret local Go test/coverage/lint workflows using tools like lazygotest, gocovsh, tparse, and golangci-lint. Do not use for Rust or non-Go projects.

Why use Go Local Health on TypingMind?

Because you install it once and use it with any model. Go Local Health is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Go Local Health in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/instructa/agent-skills/tree/main/skills/go/go-local-health. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Go Local Health?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Go Local Health?

As many as you like. As long as a model supports skills, you can use Go Local Health with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Go Local Health AI skill free?

It is published on GitHub by instructa. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇