go-engineering
Skill0 starsChanged 3 months agoLicence not identifiedView on GitHub
Write, design, and review Go the way experienced Go engineers do — idiomatic Go, API and interface design, generics, pointers vs values, error handling, concurrency, package boundaries, naming, documentation, testing, and code review. Covers structural correctness (data races, goroutine leaks, swallowed errors, context and resource handling) alongside design and style; it does not judge semantic correctness, so it will not tell you whether the code does what your requirements say. Use when writing or changing .go files, designing a Go package or public API, reviewing a Go diff or PR, deciding whether something is idiomatic Go, or running golangci-lint. Synthesizes Effective Go, the Google Go Style Guide, and Go Code Review Comments.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- cmdr-chara/chara-toolkittheir own version, first seen Nov 1, 2026
- cmdr-chara/codex-toolkittheir own version, first seen Nov 1, 2026
- alex-mextner/open-remote-commandertheir own version, first seen Oct 8, 2026
- nafeeur/MaskShifttheir own version, first seen Sep 12, 2026
- caseyng/Claude-skillstheir own version, first seen May 22, 2026
Used with
Projects with it also use rust-engineering and security-review.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
pirafrankSkillrust-engineering
Apply pragmatic Rust engineering conventions when implementing, modifying, reviewing, or refactoring Rust code. Use for Rust CLI tools, system utilities, daemons, filesystem operations, network integrations, and security-sensitive code. Based on the official Rust guidelines and selected Google Rust Style Guide practices.
Also in 3 projects that use this
SentrySkillsecurity-review
Finds exploitable application security vulnerabilities in code changes. Use for Warden security scans, appsec review, OWASP-style checks, authentication or authorization bugs, injection, XSS, SSRF, path traversal, secrets, unsafe crypto, webhook verification, open redirects, or sensitive data exposure.
Also in 3 projects that use this
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- cmdr-chara/chara-toolkit★ 2same name
- cmdr-chara/codex-toolkit★ 2same name
- nafeeur/MaskShift★ 2same name
- caseyng/Claude-skills★ 1same name
- alex-mextner/open-remote-commander★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
Show its rules and text
We split this skill into the rules it gives an agent
25 rules. 0 are common, 13 are distinctive, and 12 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
13
Distinctive
This author's own choices. Worth a look.
12
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.