How do I install the Pflow Golang Setup skill?

Run npx skillmds@latest add phpinfo/pflow-golang-setup in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Pflow Golang Setup safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Pflow Golang Setup?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Pflow Golang Setup free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Pflow Golang Setup?

phpinfo (@phpinfo) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Pflow Golang Setup by phpinfo — Agent Skill

Name: Pflow Golang Setup
Author: phpinfo

Pflow Golang Setup

Scaffolds or audits Go project infrastructure — directory layout, go.mod hygiene and tool pinning, golangci-lint v2 config, Taskfile or Makefile quality gate, GitHub Actions CI, .gitignore and repo hygiene. Detects what the project already has and fills the gaps. Use when starting a Go project, adding lint/CI/task runner, or reviewing project structure. Not for writing application code (pflow-golang) or debugging (pflow-golang-troubleshoot). Invoked manually.

phpinfo 16661eb 7 files · 29.9 KB Updated Sep 17, 2026

File contents

If setup-context.sh fails (non-zero exit or "status":"error" in its JSON) print ⚠️ <error.message> and stop. Other failing commands are findings — report and continue.

Steps

Run .agents/skills/pflow-golang-setup/scripts/setup-context.sh → {go_version, toolchain, golangci_config, golangci_config_version, task_runner, github_workflows[], remote_host, dirs[], main_packages, files_present[], go_tools, dependabot, renovate, missing[]}.
Tell the user what exists and what missing lists. Ask which gaps to fill; never overwrite an existing file — propose a diff instead.

Read the reference for each chosen item and generate the files:

Item	Read
New project, directory structure, multiple binaries, monorepo	`layout.md`
`go.mod`, `go` line, `tool` directives, versions, vendoring	`go-mod.md`
`.golangci.yml` (v2), formatters, `nolint` policy	`golangci.md`
Taskfile / Makefile: build, test, lint, race, coverage, gate	`task-runner.md`
CI workflow, caching, release, Dependabot/Renovate (when `remote_host` is `github`)	`ci-github-actions.md`

Match the project's existing choices: same task runner, same Go version as go_version, same generator tools from go_tools. Every generated gate must run locally with one command (task check / make check) and identically in CI.
Finish by running the new gate once and reporting the result, or listing the exact command the user should run if it needs tools not installed.

Paths are relative to .agents/skills/pflow-golang-setup/.

Gotchas

golangci_config_version empty or 1 with a modern golangci-lint means a v1 config: propose golangci-lint migrate, don't rewrite by hand.
Templates here are starting points; drop anything the project has no use for (a library needs no Dockerfile, a CLI needs no api/).

---name: pflow-golang-setupdescription: Scaffolds or audits Go project infrastructure — directory layout, go.mod hygiene and tool pinning, golangci-lint v2 config, Taskfile or Makefile quality gate, GitHub Actions CI, .gitignore and repo hygiene. Detects what the project already has and fills the gaps. Use when starting a Go project, adding lint/CI/task runner, or reviewing project structure. Not for writing application code (pflow-golang) or debugging (pflow-golang-troubleshoot). Invoked manually.license: MIT---If `setup-context.sh` fails (non-zero exit or `"status":"error"` in its JSON) print `⚠️ <error.message>` and stop. Other failing commands are findings — report and continue.## Steps1. Run `.agents/skills/pflow-golang-setup/scripts/setup-context.sh` → `{go_version, toolchain, golangci_config, golangci_config_version, task_runner, github_workflows[], remote_host, dirs[], main_packages, files_present[], go_tools, dependabot, renovate, missing[]}`.2. Tell the user what exists and what `missing` lists. Ask which gaps to fill; never overwrite an existing file — propose a diff instead.3. Read the reference for each chosen item and generate the files: | Item | Read | | --- | --- | | New project, directory structure, multiple binaries, monorepo | `layout.md` | | `go.mod`, `go` line, `tool` directives, versions, vendoring | `go-mod.md` | | `.golangci.yml` (v2), formatters, `nolint` policy | `golangci.md` | | Taskfile / Makefile: build, test, lint, race, coverage, gate | `task-runner.md` | | CI workflow, caching, release, Dependabot/Renovate (when `remote_host` is `github`) | `ci-github-actions.md` |4. Match the project's existing choices: same task runner, same Go version as `go_version`, same generator tools from `go_tools`. Every generated gate must run locally with one command (`task check` / `make check`) and identically in CI.5. Finish by running the new gate once and reporting the result, or listing the exact command the user should run if it needs tools not installed.Paths are relative to `.agents/skills/pflow-golang-setup/`.## Gotchas- `golangci_config_version` empty or `1` with a modern golangci-lint means a v1 config: propose `golangci-lint migrate`, don't rewrite by hand.- Templates here are starting points; drop anything the project has no use for (a library needs no Dockerfile, a CLI needs no `api/`).

Frequently asked questions