Manual service wiring becomes difficult to maintain as Go applications grow. This skill guides samber/do v2 registration, lifecycle management, modular organization, and isolated testing.
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Agent request
Review the Skillstore skill "golang-samber-do" from https://skillstore.io/skills/samber-golang-samber-do.md and its manifest at https://skillstore.io/api/skills/samber-golang-samber-do/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.
Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
All 53 static findings are false positives involving documentation syntax, Go struct tags, reference links, tool declarations, or a benign evaluation prompt. No evidence found of credential theft, unauthorized reconnaissance, data exfiltration, or prompt injection in the reviewed files. The documented Go installation command and development tools support the stated dependency injection workflow.
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
samber. (2026). golang-samber-do security audit report (audit version 1) [Author version 1.3.2]. Skillstore. https://skillstore.io/skills/samber-golang-samber-do/audits/1
BibTeX citation
@techreport{samber-samber-golang-samber-do-2026,
author = {samber},
title = {golang-samber-do security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/samber-golang-samber-do/audits/1},
note = {Author version 1.3.2}
}
CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "golang-samber-do security audit report (audit version 1)"
version: "1.3.2"
type: report
authors:
- name: "samber"
date-released: "2026-10-18"
url: "https://skillstore.io/skills/samber-golang-samber-do/audits/1"
identifiers:
- type: other
value: "skillstore:samber-golang-samber-do:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this scoreEvidence Confidence: Medium
41
Architecture
100
Maintainability
87
Content
65
Community
100
Spec Compliance
What You Can Build
Replace manual service wiring
Move application construction into modular samber/do registrations while keeping business logic independent of the container.
Manage service lifecycles
Plan shared and request-scoped dependencies, health checks, and shutdown deadlines for a Go service.
Isolate dependency tests
Reuse container configuration with clones and mock overrides to test services without production dependencies.
Try These Prompts
Create a first container
Show a minimal samber/do v2 container for a Go application. Register configuration and one service, then resolve the service with error handling.
Organize application modules
Organize my database, repository, service, and HTTP handler registrations with do.Package. Keep container access at the composition root and inject dependencies through constructors.
Test with dependency overrides
Design a samber/do v2 test for my UserService. Clone the application container, override its database dependency with a mock, and explain isolation requirements.
Review scopes and lifecycle
Review my samber/do v2 setup for request isolation, provider failures, health checks, and bounded shutdown. Propose changes and tests against my installed version.
Best Practices
Keep container access in composition and provider code; give business services explicit dependencies.
Match dependency lifetimes to application lifecycles and isolate request-specific state.
Verify examples against your installed v2 release and test provider failures, overrides, and shutdown behavior.
Avoid
Pass the injector through business logic as a service locator.
Store request-specific dependencies in the shared root container.
Copy illustrative snippets without adapting types, imports, error handling, and lifecycle cleanup.
Frequently Asked Questions
Which samber/do version does this skill target?
It targets samber/do v2 and uses the github.com/samber/do/v2 import path.
Which AI tools can use this skill?
The declared supported tools are Codex and Claude Code.
Does this skill include a runnable application?
No. It includes instructions, illustrative examples, reference guides, and evaluation prompts.
Can it help migrate manual constructor wiring?
Yes. It shows migration patterns using providers, registration packages, and resolution at the composition root.
How does it support testing?
The testing reference demonstrates container cloning, dependency overrides, mocks, and reusable container setup helpers.
Does it cover health checks and shutdown?
Yes. It explains health check methods, shutdown interfaces, signal-based shutdown, and timeout contexts.