스킬 golang-google-wire

📦

golang-google-wire

Name: golang-google-wire
Author: samber

v1.1.2 콘텐츠 리비전 r1 안전 ⚙️ 외부 명령어🌐 네트워크 접근🔑 환경 변수⚡ 스크립트 포함

Build Go Dependency Graphs with Google Wire

Go dependency graphs become difficult to maintain as constructors and interfaces change. This skill guides Wire provider design, injector generation, cleanup handling, and testing.

지원: Codex Code(CC)

🥉 78 브론즈

Maintain this Skill? Claim it 🥉 78 브론즈

내 에이전트로 설치

이 요청을 에이전트에 복사하세요. 공식 Skill 페이지와 매니페스트가 포함되어 있습니다.

에이전트 요청

Review the Skillstore skill "golang-google-wire" from https://skillstore.io/skills/samber-golang-google-wire.md and its manifest at https://skillstore.io/api/skills/samber-golang-google-wire/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

에이전트는 계속해서 계획을 표시하고 보안 정책에서 요구하는 확인을 요청해야 합니다.

에이전트가 읽기 쉬운 리소스

AI 에이전트, 크롤러, 스크립트가 전체 페이지 대신 정리된 컨텍스트만 필요할 때 이 링크를 사용하세요.

Markdown 상세 GET /skills/samber-golang-google-wire.md 서명된 manifest GET /api/skills/samber-golang-google-wire/manifest 서명된 lockfile GET /api/skills/samber-golang-google-wire/lockfile

테스트해 보기

"golang-google-wire" 사용 중입니다. Wire generates my injector, but go build reports that InitApp is declared twice.

예상 결과:

The injector stub needs the wireinject build constraint. Exclude the stub from normal builds, regenerate the injector, and build again.

"golang-google-wire" 사용 중입니다. Both database connection providers return strings, and Wire reports multiple bindings.

예상 결과:

Use distinct named types for primary and replica connection strings. Update the providers and database constructors so each dependency has a unique type.

"golang-google-wire" 사용 중입니다. How can my integration tests replace the production mailer without changing production wiring?

예상 결과:

Create a test provider set that binds the mailer interface to a recording fake. Compose the test graph without the conflicting production mailer binding.

보안 감사

안전

v1 • 2026. 10. 18. 버전별 보고서 열기

All 76 static findings are false positives involving documentation formatting, Go syntax, example configuration, or legitimate development commands. No evidence found of credential exfiltration, unauthorized email delivery, system reconnaissance, or malicious prompt injection. The skill documents dependency installation and code generation, which require normal development permissions.

스캔된 파일

1,193

분석된 줄 수

검토 항목

오탐 무시됨

위험 요인

⚙️ 외부 명령어 (50)

evals/evals.json:6 evals/evals.json:35 evals/evals.json:64 evals/evals.json:93 evals/evals.json:122 evals/evals.json:151 evals/evals.json:180 evals/evals.json:206 references/advanced.md:130-131 references/advanced.md:131-135 SKILL.md:3 SKILL.md:27 SKILL.md:31 SKILL.md:35 SKILL.md:37 SKILL.md:43 SKILL.md:44 SKILL.md:47-50 SKILL.md:50-57 SKILL.md:57 SKILL.md:60-62 SKILL.md:62-68 SKILL.md:68-75 SKILL.md:75-79 SKILL.md:79-81 SKILL.md:81-95 SKILL.md:95-99 SKILL.md:99-101 SKILL.md:101-103 SKILL.md:103-115 SKILL.md:115-117 SKILL.md:117 SKILL.md:121-125 SKILL.md:125-131 SKILL.md:131-136 SKILL.md:136-142 SKILL.md:142 SKILL.md:144-150 SKILL.md:150-152 SKILL.md:152 SKILL.md:158-161 SKILL.md:161-165 SKILL.md:165-183 SKILL.md:183-185 SKILL.md:185-189 SKILL.md:189-192 SKILL.md:192-194 SKILL.md:194 SKILL.md:198 SKILL.md:199-200

🌐 네트워크 접근 (4)

evals/evals.json:235 SKILL.md:12 SKILL.md:39 SKILL.md:235

🔑 환경 변수 (1)

references/recipes.md:51

⚡ 스크립트 포함 (1)

references/testing.md:42-45

가장 최근에 완료된 정적·의미론적 감사에서 확인된 보안 발견 사항이 감지되지 않았습니다. 이는 스킬에 부작용이 없음을 증명하지 않습니다.

감사자: codex

이 보고서 공유 및 인용

버전이 지정된 평가 보고서, 중립 배지, 임베드 카드 및 인용을 공유하세요. Skillstore는 근거를 보고하지만 이 Skill의 안전 여부를 판단하지 않습니다.

버전별 보고서 열기

보고서 링크 복사

https://skillstore.io/skills/samber-golang-google-wire/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown 배지

[![Skillstore security assessment](https://skillstore.io/badges/skills/samber-golang-google-wire/security.svg)](https://skillstore.io/skills/samber-golang-google-wire?utm_source=security_passport_badge)

HTML 배지

<a href="https://skillstore.io/skills/samber-golang-google-wire?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/samber-golang-google-wire/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

임베드 카드

<iframe src="https://skillstore.io/embed/skills/samber-golang-google-wire.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

학술 인용 (APA · BibTeX · CFF)

APA 인용

samber. (2026). golang-google-wire security audit report (audit version 1) [Author version 1.1.2]. Skillstore. https://skillstore.io/skills/samber-golang-google-wire/audits/1

BibTeX 인용

@techreport{samber-samber-golang-google-wire-2026,
  author = {samber},
  title = {golang-google-wire security audit report (audit version 1)},
  institution = {Skillstore},
  year = {2026},
  number = {1},
  url = {https://skillstore.io/skills/samber-golang-google-wire/audits/1},
  note = {Author version 1.1.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-google-wire security audit report (audit version 1)"
version: "1.1.2"
type: report
authors:
  - name: "samber"
date-released: "2026-10-18"
url: "https://skillstore.io/skills/samber-golang-google-wire/audits/1"
identifiers:
  - type: other
    value: "skillstore:samber-golang-google-wire:audit:1"
    description: "Skillstore immutable audit report identifier"

Skillstore 점수

이 점수의 이유 증거 신뢰도: 중간

아키텍처

100

유지보수성

콘텐츠

커뮤니티

사양 준수

만들 수 있는 것

Add compile-time application wiring

Organize database, cache, repository, and service constructors into reusable provider sets with a generated application injector.

Maintain generated dependency graphs

Plan regeneration and CI checks after constructor changes, and keep generated source synchronized with provider definitions.

Replace dependencies in integration tests

Design test provider sets and explicit interface bindings that replace production dependencies with controlled fakes.

이 프롬프트를 사용해 보세요

Understand a basic Wire injector

Explain how Google Wire connects these constructors: [constructor signatures]. Show the provider set, injector build constraint, and generation workflow.

Fix a provider resolution error

Diagnose this Wire error: [error]. Review these providers and interfaces: [code]. Explain the smallest binding or named-type change needed.

Design cleanup-aware application wiring

Design Wire provider sets for [application components]. Include cleanup signatures, partial failure handling, prebuilt configuration arguments, and the caller's shutdown responsibilities.

Plan test wiring and CI verification

Review this Wire layout: [provider sets and injectors]. Plan fake interface bindings, test generation, and CI freshness checks. Identify build-tag and lifecycle risks.

모범 사례

Regenerate and review Wire output after constructor changes, then commit generated source with the provider changes.
Keep provider sets small and bind interfaces explicitly near their concrete providers.
Propagate cleanup functions through injectors and handle construction errors before scheduling cleanup.

피하기

Editing generated injector bodies instead of changing providers and regenerating.
Providing multiple values of the same type without distinct named types.
Treating Wire as a runtime lifecycle framework with automatic startup and shutdown hooks.

자주 묻는 질문

What does Google Wire generate?

Wire generates ordinary Go constructor calls from provider sets and injector declarations. The resulting application does not need a runtime dependency container.

Does this skill install Go or Wire?

No tools are bundled. The instructions include installation commands, which require network access and permission to modify the development environment.

Should I edit wire_gen.go to fix constructor errors?

No. Update the providers or injector declarations, regenerate the output, and review the changes.

How are interfaces connected to implementations?

Use explicit wire.Bind declarations when providers return concrete implementations. Keep the concrete provider available in the relevant set.

Does Wire manage graceful shutdown?

Wire can compose provider cleanup functions. You must still implement lifecycle coordination, signal handling, and graceful server shutdown.

Is Google Wire still maintained?

The included documentation identifies Google Wire as archived. Verify current upstream status and Go compatibility before selecting it for a new project.