golang-modernize

Modernize Golang code to use recent language features, standard library improvements, and idiomatic patterns. Trigger proactively when writing or reviewing Go code and old-style patterns are detected, or when encountering a deprecation warning. Also use when the user explicitly asks for modernization, a Go version upgrade, or a CI/tooling refresh.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable and well-structured, with strong progressive disclosure and a validated multi-step workflow. The only drag is mild redundancy from restating the full-scan sub-agent plan and re-narrating the description.

Suggestions

Remove the duplicate five-sub-agent description: keep it in the Modes/Full-scan section and have workflow step 7 cross-reference it instead of re-listing the categories.

Delete or compress the opening restatement ("This skill helps you continuously modernize Go codebases...") since the frontmatter description already covers it.

Consolidate the repeated worktree-isolation rationale (Modes section and step 7) into a single mention.

Dimension	Reasoning	Score
Conciseness	Mostly efficient dense tables, but the five-sub-agent full-scan description is restated (Modes section and workflow step 7) and the opening re-narrates the description; these could be tightened.	2 / 3
Actionability	Concrete package-replacement tables with "Since" versions, a versioned migration priority guide, specific commands (go mod tidy, golangci-lint, govulncheck), and a copy-ready .modernize file format.	3 / 3
Workflow Clarity	A nine-step sequenced workflow with explicit validation (run tests, verify compatibility), a consent check, and worktree isolation for the batch rewrite — checkpoints are present rather than implicit.	3 / 3
Progressive Disclosure	SKILL.md is a concise overview with clearly signaled one-level-deep links to real files (./references/versions.md, ./references/tooling.md); detailed before/after examples are correctly pushed to references.	3 / 3
	Total	11 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: third-person voice, concrete actions, explicit trigger guidance for both proactive and explicit use, and a well-scoped niche. It cleanly satisfies all four dimensions.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "use recent language features, standard library improvements, and idiomatic patterns" plus "Go version upgrade" and "CI/tooling refresh" — rather than vague abstractions.	3 / 3
Completeness	Explicitly states what it does ("Modernize Golang code...") and when to trigger via a clear "Trigger proactively when... Also use when..." clause covering both contextual and explicit invocations.	3 / 3
Trigger Term Quality	Covers natural terms a user would say: "modernization", "Go version upgrade", "CI/tooling refresh", "deprecation warning", and "writing or reviewing Go code".	3 / 3
Distinctiveness Conflict Risk	The Go-modernization niche with triggers tied to old-style patterns and deprecation warnings is clearly distinct from general Go skills and unlikely to misfire.	3 / 3
	Total	12 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_field	'metadata' should map string keys to string values	Warning

	Total	15 / 16 Passed

Repository: samber/cc-skills-golang
Path: skills/golang-modernize/SKILL.md
Commit: 4158351

Reviewed: about 14 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.