Add ub-go skill for Go development - #2
Open
Zyra-V21 wants to merge 1 commit into
Open
Conversation
New language skill following the same structure as ub-python and ub-ts: SKILL.md contract, portable standards reference with official source map, repository workflow discovery, golangci-lint config resolution, and a copy-if-missing scaffold for repos without lint config. Registered in AGENTS.md, README, marketplace.json, the docs sidebar, and the skill catalog index. All repo maintenance checks pass.
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
1 participant
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.
This adds a Go language skill built on the same structure and principles as ub-python and ub-ts: repo truth first, modern patterns for new code, bounded legacy exceptions, and validation after edits.
Contents:
SKILL.mdwith the usual contract: routing description, core workflow, version and research policy with OFFICIAL_CONFLICT/UNVERIFIED disclosures, implementation rules, legacy guardrails, output requirements, and completion checklist.references/go-standards.md: portable modern Go baseline (module and toolchain truth, small consumer-side interfaces, generics discipline, error wrapping, structured concurrency, modern stdlib preferences such aslog/slog,slices/maps/cmp,os.Rootandtesting/synctest, testing practice) with an official source map.references/repository-go-workflows.md: resolving a repo's actual Go version, build, and validation truth before recommending commands.references/golangci-config-resolution.md: lint config discovery order, config format awareness, and scaffold behavior.assets/golangci-template/.golangci.ymlplusscripts/scaffold_golangci.py: copy-if-missing starter using the current v2 config schema, same pattern as the Ruff scaffold in ub-python. It refuses to write anything if any golangci config already exists.Validation: check_repo_catalog, check_package_metadata, check_repo_paths and check_skill_schema all pass, check-docs-sync reports nothing for this skill, the scaffold script passes ruff with the repo config, and the template passes yamllint with the repo settings.
There is a companion PR adding ub-rust. Both touch the shared catalog files (skill count and tables), so whichever lands second will need a small rebase; I can take care of that.
I tried to stay close to how ub-python and ub-ts are written, but if any of it does not fit how you want language skills to evolve (naming, scope, the scaffold, the reference split), I am happy to rework it. Feedback very welcome.