go-programming
Skill4 starsChanged 5 months agoMITView on GitHub
Go software engineering skill for designing, implementing, debugging, testing, reviewing, and refactoring Go applications, CLIs, APIs, services, concurrency code, modules, and tooling. Use for .go files, go.mod/go.sum, goroutines/channels, interfaces, error handling, performance profiling, race fixes, and idiomatic Go architecture.
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 6 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Prefer small interfaces at consumer boundaries, explicit errors, table-driven tests, and simple composition over abstraction.
- Very specific: line 13
Run targeted go test first, then wider tests when feasible.
- Distinctive: line 20
Add or update tests for success paths, failure paths, edge cases, and races.
- Distinctive: line 21
Verify with formatting, tests, vet/static analysis if available, and a concise summary of risks.
- Very specific: line 25
Use context.Context as the first parameter for request-scoped work.
- Distinctive: line 27
Keep goroutine lifecycle explicit with cancellation, bounded queues, and ownership of channel close.
- Distinctive: line 28
Avoid package globals unless they are immutable constants or intentionally shared.
- Distinctive: line 29
Use benchmarks and profiles before performance rewrites.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Go Programming
Operating Rules
- Inspect
go.mod, package layout, tests, and existing style before changing code. - Prefer small interfaces at consumer boundaries, explicit errors, table-driven tests, and simple composition over abstraction.
- Preserve exported API compatibility unless the user asks for a breaking change.
- Run targeted
go testfirst, then wider tests when feasible. Usego test -racefor concurrency changes when practical.
Workflow
- Build context with
rg --files,go list ./..., and targeted reads of affected packages. - Identify package boundaries, public types, side effects, and concurrency ownership.
- Implement the smallest cohesive change with clear errors and context-aware cancellation.
- Add or update tests for success paths, failure paths, edge cases, and races.
- Verify with formatting, tests, vet/static analysis if available, and a concise summary of risks.
Go Standards
- Use
context.Contextas the first parameter for request-scoped work. - Wrap errors with
%wwhen callers can act on the cause; avoid string matching. - Keep goroutine lifecycle explicit with cancellation, bounded queues, and ownership of channel close.
- Avoid package globals unless they are immutable constants or intentionally shared.
- Use benchmarks and profiles before performance rewrites.
Other versions1 project uses a version of this.
Word for word · 1
- Garyson26/Trident-SecOps-Skills★ 1100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
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.
In this repository45 other files it gives its agents.
- ai-redteamSkill
- api-security-automationSkill
- assembly-programmingSkill
- bug-bounty-workflowSkill
- claude-mythos-emulationSkill
- cloud-security-automationSkill
- cybersecurity-partnerSkill
- detection-engineeringSkill
- devsecopsSkill
- exploit-developmentSkill
- forensics-triageSkill
- gemini-tool-orchestratorSkill
- kubernetes-securitySkill
- malware-reverse-engineeringSkill
- multilingualSkill
- offensive-securitySkill
- prompt-enhancementSkill
- python-programmingSkill
- ai-redteamSkill
- api-security-automationSkill
- assembly-programmingSkill
- bug-bounty-workflowSkill
- claude-mythos-emulationSkill
- cloud-security-automationSkill
- cybersecurity-partnerSkill
- detection-engineeringSkill
- devsecopsSkill
- exploit-developmentSkill
- forensics-triageSkill
- gemini-tool-orchestratorSkill
- go-programmingSkill
- kubernetes-securitySkill
- malware-reverse-engineeringSkill
- multilingualSkill
- offensive-securitySkill
- osint-recon-automationSkill
- prompt-enhancementSkill
- purple-team-automationSkill
- python-programmingSkill
- smart-contract-auditSkill
- soc-operationsSkill
- threat-intel-fusionSkill
- smart-contract-auditSkill
- soc-operationsSkill
- threat-intel-fusionSkill
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.

