Name: golang-modernize
Rating: 65.60000000000001 (1 reviews)
Author: samber

golang-modernize

Modernize Golang code to use recent language features, standard library improvements, and idiomatic patterns. Use when reviewing Go code with old-style patterns, when encountering a deprecation warning, or when the user asks for modernization, a Go version upgrade (e.g. to Go 1.27), or a CI/tooling refresh. Not for structural refactors, extracting functions, or moving code between packages (→ See `samber/cc-skills-golang@golang-refactoring` skill).

Quality

79%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/golang-modernize/SKILL.md

Quality

Content

71%Weight 40%Scale 1-5

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

A well-organized, actionable modernization guide with a clear sequenced workflow, validation checkpoints, and clean progressive disclosure to two real reference files. The main weakness is repetition of the five-sub-agent fan-out description across three sections, which inflates token cost without adding clarity.

Suggestions

Describe the five sub-agent fan-out once (e.g. in Full-scan mode) and reference it from the Orchestration-mode paragraph and Workflow step 7 instead of restating all five agents each time.

Add an explicit "if lint/tests fail → fix → re-run" feedback loop in Workflow step 5 to match the validation rigor of the dependency-update step.

Trim the Scope paragraph and the "TRY TO CONVINCE" aside, which read as filler against an otherwise lean guide.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and assumes Claude's Go knowledge, but the five-sub-agent breakdown is restated three times (Orchestration mode, Full-scan mode, and Workflow step 7) and the scope/persona prose could be tightened, so some trimming is warranted.	3 / 5
Actionability	Provides concrete commands (go test ./..., golangci-lint, go mod tidy, go fix ./...), a deprecated→replacement table with versions, and a worked .modernize file format; detailed before/after examples are appropriately deferred to references, leaving minor gaps inline.	4 / 5
Workflow Clarity	A clear nine-step sequenced workflow with validation checkpoints (run golangci-lint + go test, go mod tidy + test suite before dep updates, isolated worktree for batch sweeps, Go 1.27 risk checklist) and a feedback loop via .modernize; a few fix-and-retry loops are implicit rather than spelled out.	4 / 5
Progressive Disclosure	SKILL.md is a well-structured overview with clearly signaled, verified one-level-deep references (./references/versions.md and ./references/tooling.md, including an anchor link); detailed per-version examples and tooling deep-dives are appropriately split into those files.	5 / 5
	Total	16 / 20 Passed

Description

87%Weight 40%Scale 1-5

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, well-scoped description that clearly states what the skill does, when to invoke it via concrete trigger phrases, and where its boundary lies against a sibling refactoring skill. Minor specificity gains would come from naming a few concrete before/after modernizations directly.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete modernization categories ("recent language features, standard library improvements, and idiomatic patterns", "deprecation warning", "Go version upgrade", "CI/tooling refresh"), with only minor gaps in fully enumerating concrete actions.	4 / 5
Completeness	Explicitly answers both what ("Modernize Golang code to use recent language features, standard library improvements, and idiomatic patterns") and when ("Use when reviewing Go code with old-style patterns, when encountering a deprecation warning, or when the user asks for modernization, a Go version upgrade... or a CI/tooling refresh") with concrete trigger phrases, plus a negative-scope clause.	5 / 5
Trigger Term Quality	Includes natural phrases users would say ("reviewing Go code with old-style patterns", "deprecation warning", "modernization", "Go version upgrade", "CI/tooling refresh"); a few synonyms or file-extension terms are absent but coverage is strong.	4 / 5
Distinctiveness Conflict Risk	Clear Go-modernization niche with distinct triggers and an explicit boundary ("Not for structural refactors, extracting functions, or moving code between packages → See golang-refactoring skill"), minimizing conflict with adjacent skills.	5 / 5
	Total	18 / 20 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: 19a0626

Reviewed: 2 days 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.