Table-driven tests, subtests, benchmarks, fuzzing, and golden files for Go TDD workflows.
Automate repetitive workflows and reduce manual effort
Example: Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example: Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example: Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Time estimate: 15-45 minutes depending on use case complexity
Prerequisites
Submit your Claude Code skill and start earning
epx add affaan-m/everything-claude-code --skill golang-testingCompatible with
Supported agents
Covers the RED-GREEN-REFACTOR cycle with step-by-step examples for writing tests before implementation
Includes table-driven test patterns for comprehensive coverage, error cases, and parallel execution with t.Run()
Provides benchmarking techniques for performance analysis, memory allocation tracking, and comparative benchmarks across input sizes
Supports fuzzing with seed corpus and property
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiongolang-testingExecute the skills CLI command in your project's root directory to begin installation:
epx add affaan-m/everything-claude-code --skill golang-testingFetches golang-testing from affaan-m/everything-claude-code and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
.cursor/skills/golang-testing
Restart Cursor to activate golang-testing. Access via /golang-testingin your agent's command palette.
Learn more:View source on GitHubSkills CLI docsAbout CursorWhat are agent skills?
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
django-patterns
affaan-m/everything-claude-code · Backend · same repo
deep-research
affaan-m/everything-claude-code · Productivity · same repo
frontend-testing-best-practices
sergiodxa/agent-skills · Frontend · tag: testing
typescript-best-practices
jwynia/agent-skills · Backend · same category
java-springboot
github/awesome-copilot · Backend · same category
fastapi-expert
jeffallan/claude-skills · Backend · same category
Registry listing for golang-testing matched our evaluation — installs cleanly and behaves as described in the markdown.
We added golang-testing from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
golang-testing reduced setup friction for our internal harness; good balance of opinion and flexibility.
Registry listing for golang-testing matched our evaluation — installs cleanly and behaves as described in the markdown.
Useful defaults in golang-testing — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
golang-testing reduced setup friction for our internal harness; good balance of opinion and flexibility.
We added golang-testing from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Keeps context tight: golang-testing is the kind of skill you can hand to a new teammate without a long onboarding doc.
golang-testing reduced setup friction for our internal harness; good balance of opinion and flexibility.
Useful defaults in golang-testing — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 65