Improved and evaluated Go skills#9
Open
spoenemann wants to merge 1 commit into
Open
Conversation
montymxb
approved these changes
Jul 7, 2026
montymxb
left a comment
montymxb
left a comment
Member
There was a problem hiding this comment.
Just some small suggestions, rest looks good!
| --- | ||
| name: go-documentation | ||
| description: Write idiomatic Go doc comments that render correctly on pkg.go.dev. Use whenever the user is writing or reviewing Go documentation — package comments, `doc.go` files, exported symbol comments, testable `Example` functions, deprecation notices — or wants to publish a module to pkg.go.dev, preview docs locally with `pkgsite`, or debug a broken pkg.go.dev page. Do not use for general Go programming questions or non-Go languages. | ||
| description: Write idiomatic Go doc comments that render correctly on pkg.go.dev — package comments, `doc.go`, exported-symbol comments, testable `Example` functions, deprecation notices — and publish or debug modules on pkg.go.dev (`pkgsite`, the module proxy). Use when writing or reviewing Go documentation, or when a developer used to JSDoc/TSDoc/Markdown is unsure how Go doc comments differ. Not for general Go programming or non-Go languages. |
Member
There was a problem hiding this comment.
small rewording suggestion
Suggested change
| description: Write idiomatic Go doc comments that render correctly on pkg.go.dev — package comments, `doc.go`, exported-symbol comments, testable `Example` functions, deprecation notices — and publish or debug modules on pkg.go.dev (`pkgsite`, the module proxy). Use when writing or reviewing Go documentation, or when a developer used to JSDoc/TSDoc/Markdown is unsure how Go doc comments differ. Not for general Go programming or non-Go languages. | |
| description: Write idiomatic Go doc comments that render correctly on pkg.go.dev — package comments, `doc.go`, exported-symbol comments, testable `Example` functions, deprecation notices — and publish or debug modules on pkg.go.dev (`pkgsite`, the module proxy). Use when writing or reviewing Go documentation, or when a developer used to writing JSDoc/TSDoc/Markdown is unsure how Go doc comments differ. Not for general Go programming or non-Go languages. |
| ## Coming from TypeScript | ||
|
|
||
| Load these as needed — don't read them upfront. The main SKILL.md has the conventions and decision points; the references hold operational detail. | ||
| A Go doc comment is a plain `//` comment above a declaration — there are no tags, and almost none of the Markdown that JSDoc/TSDoc allow. These are the habits that silently produce wrong or unrendered docs; reach for the Go column instead. |
Member
There was a problem hiding this comment.
Would it make sense to break this into a separate reference so it can be loaded when specifically needed? I can see the skill description notes this capability specifically, but I'm wondering if it would make sense to separate that a bit.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
idiomatic-goandgo-documentationin several iterationsskill-evalsidiomatic-goSkill eval results
idiomatic-go
Model:
composer-2.5-fastUsefulness: Post–iteration-4 edits clearly pay off. The skill steers agents toward production-ready concurrency, language-engineering, and TypeScript-to-Go port patterns that baselines miss.
go-documentation
Model:
claude-haiku-4-5Usefulness: Reliable wins on first-sentence naming,
[Name]doc links in package overviews, and testableExampleconventions. Attachment/JSDoc-stripping guidance holds as regression guards. Materially improves pkg.go.dev–ready documentation over baseline.