Run any Skill in Manus with one click

golang-code-audit

Stars0

Forks0

UpdatedJune 7, 2026 at 08:23

Audit existing Go and Golang codebases, pull requests, diffs, packages, services, CLIs, tests, build pipelines, and repository layouts against idiomatic Go development guidance. Use when reviewing, auditing, assessing, evaluating, inspecting, checking best-practice compliance, finding violations, identifying risks, or producing findings for already-built Go code.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

Zate

Zate/golang-development

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

File Explorer

2 files

SKILL.md

readonly

name	golang-code-audit
description	Audit existing Go and Golang codebases, pull requests, diffs, packages, services, CLIs, tests, build pipelines, and repository layouts against idiomatic Go development guidance. Use when reviewing, auditing, assessing, evaluating, inspecting, checking best-practice compliance, finding violations, identifying risks, or producing findings for already-built Go code.

Go Code Audit

Workflow

Determine the audit scope: whole repo, diff, package, command, service, tests, CI/build, or release path.
Inspect go.mod, go.work, package layout, relevant source files, tests, build scripts, and configured quality commands before judging.
Select companion skills by risk area:
- golang-planning-layout for module layout, package boundaries, command structure, and naming.
- golang-architecture-patterns for dependency direction, interfaces, services, adapters, repositories, APIs, and concurrency boundaries.
- golang-implementation-idioms for naming, errors, context, nil handling, generics, comments, and standard library usage.
- golang-testing for coverage gaps, test boundaries, fakes, determinism, benchmarks, fuzzing, and race checks.
- golang-quality-linting for format, vet, static analysis, security, linter configuration, and completion gates.
- golang-build-deploy for release, packaging, Docker, CI, runtime config, graceful shutdown, and deployment readiness.
Run or request the narrowest verification commands that are safe and relevant. If a command cannot be run, state that as residual risk.
Produce findings first, ordered by severity, with file and line references when possible.
Separate correctness, security, race/leak, API breakage, test gaps, maintainability, and style findings.
Do not include broad rewrites, unrelated refactors, or stylistic preferences unless they materially affect maintainability or match the requested audit scope.

Output Shape

Start with findings. If none, say no issues found.
For each finding include severity, location, concrete risk, and the smallest useful remediation.
Add open questions or assumptions only after findings.
End with verification performed and remaining test or inspection gaps.

More from this repository

same repository

golang-architecture-patterns

Zate/golang-development

Design or audit Go application architecture, package boundaries, dependency direction, interfaces, adapters, repositories, services, HTTP handlers, concurrency boundaries, and maintainable design patterns. Use for Golang service design, refactors, domain layering, dependency injection, ports/adapters, repository patterns, functional options, API design, concurrency architecture, or reviewing existing Go architecture for coupling and maintainability risks.

2026-06-070

golang-build-deploy

Zate/golang-development

Build, package, release, containerize, deploy, or audit Go applications and CLIs. Use for Golang build flags, module release checks, cross-compilation, Dockerfiles, CI/CD, version metadata, graceful shutdown, runtime configuration, security updates, production deployment plans, or reviewing existing Go release/deployment readiness.

2026-06-070

golang-development-workflow

Zate/golang-development

Route Go and Golang development work into the right build or audit workflow. Use for broad Go tasks such as building features, implementing changes, refactoring, planning, reviewing, auditing, assessing an existing codebase, checking against Go best practices, or deciding which Golang Development skills apply.

2026-06-070

golang-implementation-idioms

Zate/golang-development

Implement or audit idiomatic Go code using effective naming, errors, context, interfaces, generics, nil handling, slices/maps, documentation comments, and standard library conventions. Use when writing, refactoring, cleaning, or reviewing Golang code; reducing nesting; improving API ergonomics; checking idiomatic implementation style; or finding non-idiomatic Go in existing code.

2026-06-070

golang-planning-layout

Zate/golang-development

Plan or audit idiomatic Go modules, repository layout, package boundaries, command structure, migration strategy, and implementation plans. Use when working on Go or Golang projects before adding packages, moving code, choosing cmd/internal/pkg layout, splitting modules, introducing workspaces, writing a multi-step implementation plan, or reviewing an existing repo for layout and package-boundary problems.

2026-06-070

golang-quality-linting

Zate/golang-development

Verify, improve, or audit Go code quality with gofmt, goimports, go vet, static analysis, golangci-lint, security checks, code review, lint configuration, and completion verification. Use when reviewing Golang changes, fixing linter failures, setting up golangci-lint, deciding quality gates, auditing existing quality practices, or checking whether Go code is ready to ship.

2026-06-070

name	golang-code-audit
description	Audit existing Go and Golang codebases, pull requests, diffs, packages, services, CLIs, tests, build pipelines, and repository layouts against idiomatic Go development guidance. Use when reviewing, auditing, assessing, evaluating, inspecting, checking best-practice compliance, finding violations, identifying risks, or producing findings for already-built Go code.

Go Code Audit

Workflow

Determine the audit scope: whole repo, diff, package, command, service, tests, CI/build, or release path.
Inspect go.mod, go.work, package layout, relevant source files, tests, build scripts, and configured quality commands before judging.
Select companion skills by risk area:
- golang-planning-layout for module layout, package boundaries, command structure, and naming.
- golang-architecture-patterns for dependency direction, interfaces, services, adapters, repositories, APIs, and concurrency boundaries.
- golang-implementation-idioms for naming, errors, context, nil handling, generics, comments, and standard library usage.
- golang-testing for coverage gaps, test boundaries, fakes, determinism, benchmarks, fuzzing, and race checks.
- golang-quality-linting for format, vet, static analysis, security, linter configuration, and completion gates.
- golang-build-deploy for release, packaging, Docker, CI, runtime config, graceful shutdown, and deployment readiness.
Run or request the narrowest verification commands that are safe and relevant. If a command cannot be run, state that as residual risk.
Produce findings first, ordered by severity, with file and line references when possible.
Separate correctness, security, race/leak, API breakage, test gaps, maintainability, and style findings.
Do not include broad rewrites, unrelated refactors, or stylistic preferences unless they materially affect maintainability or match the requested audit scope.

Output Shape

Start with findings. If none, say no issues found.
For each finding include severity, location, concrete risk, and the smallest useful remediation.
Add open questions or assumptions only after findings.
End with verification performed and remaining test or inspection gaps.