golang-google-wire
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.
Mit meinem Agent installieren
Kopieren Sie diese Anfrage in Ihren Agent. Sie enthält die maßgebliche Skill-Seite und das Manifest.
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.Ihr Agent sollte weiterhin seinen Plan anzeigen und alle von der Sicherheitsrichtlinie verlangten Bestätigungen anfordern.
Agent-lesbare Ressourcen
Verwenden Sie diese Links, wenn ein KI-Agent, Crawler oder Skript sauberen Kontext benötigt, statt die vollständige Seite zu lesen.
Testen
„golang-google-wire“ wird verwendet. Wire generates my injector, but go build reports that InitApp is declared twice.
Erwartetes Ergebnis:
The injector stub needs the wireinject build constraint. Exclude the stub from normal builds, regenerate the injector, and build again.
„golang-google-wire“ wird verwendet. Both database connection providers return strings, and Wire reports multiple bindings.
Erwartetes Ergebnis:
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“ wird verwendet. How can my integration tests replace the production mailer without changing production wiring?
Erwartetes Ergebnis:
Create a test provider set that binds the mailer interface to a recording fake. Compose the test graph without the conflicting production mailer binding.
Sicherheitsaudit
SicherAll 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.
Risikofaktoren
⚙️ Externe Befehle (50)
🌐 Netzwerkzugriff (4)
🔑 Umgebungsvariablen (1)
⚡ Enthält Skripte (1)
Diesen Bericht teilen & zitieren
Teile den versionierten Bewertungsbericht, das neutrale Badge, die Einbettungskarte und Zitate. Skillstore berichtet Nachweise, ohne zu entscheiden, ob dieser Skill sicher ist.
Berichtslink kopieren
https://skillstore.io/skills/samber-golang-google-wire/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown-Badge
[](https://skillstore.io/skills/samber-golang-google-wire?utm_source=security_passport_badge)HTML-Badge
<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>Einbettungskarte
<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>Wissenschaftliche Zitate (APA · BibTeX · CFF)
APA-Zitat
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/1BibTeX-Zitat
@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-Score
Warum dieser Score Evidenzvertrauen: MittelWas Sie erstellen können
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.
Diese Prompts ausprobieren
Explain how Google Wire connects these constructors: [constructor signatures]. Show the provider set, injector build constraint, and generation workflow.
Diagnose this Wire error: [error]. Review these providers and interfaces: [code]. Explain the smallest binding or named-type change needed.
Design Wire provider sets for [application components]. Include cleanup signatures, partial failure handling, prebuilt configuration arguments, and the caller's shutdown responsibilities.
Review this Wire layout: [provider sets and injectors]. Plan fake interface bindings, test generation, and CI freshness checks. Identify build-tag and lifecycle risks.
Bewährte Praktiken
- 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.
Vermeiden
- 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.
Häufig gestellte Fragen
What does Google Wire generate?
Does this skill install Go or Wire?
Should I edit wire_gen.go to fix constructor errors?
How are interfaces connected to implementations?
Does Wire manage graceful shutdown?
Is Google Wire still maintained?
Entwicklerdetails
Autor
samberLizenz
MIT
Autorenversion
v1.1.2
Skillstore-Revision
r1
Ref.
29fe30832fbade762d737579eea5c4bf3e480de7
Aktualität der Wartung
18.10.2026
Nutzung
0 Downloads · 0 Aufrufe
Dateistruktur