golang-uber-fx
Build Go Services with Uber Fx
Complex Go services need predictable dependency wiring and lifecycle management. This skill provides practical Uber Fx guidance for modular applications, graceful shutdown, and focused tests.
自分のエージェントでインストール
このリクエストをエージェントにコピーしてください。正規の Skill ページとマニフェストが含まれています。
Review the Skillstore skill "golang-uber-fx" from https://skillstore.io/skills/samber-golang-uber-fx.md and its manifest at https://skillstore.io/api/skills/samber-golang-uber-fx/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。
エージェントが読めるリソース
AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。
テストする
「golang-uber-fx」を使用しています。 A server constructor starts listening immediately and blocks application startup.
期待される結果:
- Move listener creation and serving into an OnStart hook.
- Start the blocking serve loop in a goroutine so OnStart returns promptly.
- Register an OnStop hook that performs graceful shutdown with the provided context.
「golang-uber-fx」を使用しています。 HTTP, database, metrics, and worker providers are mixed in one composition root.
期待される結果:
- Create one Fx module for each service area.
- Keep shared configuration and logging providers at the application root.
- Place concern-specific providers, invokes, and decorators inside their owning modules.
「golang-uber-fx」を使用しています。 An integration test needs an erroring database without changing the production module.
期待される結果:
- Compose the existing production module in an fxtest application.
- Replace the database interface with the erroring fake.
- Populate the service under test, start the application, assert behavior, and stop it.
セキュリティ監査
安全All 88 static findings are false positives. Backtick alerts come from Markdown and Go literals, not command execution. Other matches are benign prompts, examples, official links, metadata, and local test behavior.
リスク要因
⚙️ 外部コマンド (50)
🌐 ネットワークアクセス (7)
📁 ファイルシステムへのアクセス (1)
🔑 環境変数 (2)
⚡ スクリプトを含む (1)
このレポートを共有・引用
バージョン付き評価レポート、中立的なバッジ、埋め込みカード、引用を共有できます。Skillstore は証拠を報告しますが、この Skill が安全かどうかは判断しません。
レポートリンクをコピー
https://skillstore.io/skills/samber-golang-uber-fx/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdownバッジ
[](https://skillstore.io/skills/samber-golang-uber-fx?utm_source=security_passport_badge)HTMLバッジ
<a href="https://skillstore.io/skills/samber-golang-uber-fx?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/samber-golang-uber-fx/security.svg" alt="Skillstore security assessment" loading="lazy"></a>埋め込みカード
<iframe src="https://skillstore.io/embed/skills/samber-golang-uber-fx.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-uber-fx security audit report (audit version 1) [Author version 1.2.2]. Skillstore. https://skillstore.io/skills/samber-golang-uber-fx/audits/1BibTeX形式の引用
@techreport{samber-samber-golang-uber-fx-2026,
author = {samber},
title = {golang-uber-fx security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/samber-golang-uber-fx/audits/1},
note = {Author version 1.2.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-uber-fx security audit report (audit version 1)"
version: "1.2.2"
type: report
authors:
- name: "samber"
date-released: "2026-09-23"
url: "https://skillstore.io/skills/samber-golang-uber-fx/audits/1"
identifiers:
- type: other
value: "skillstore:samber-golang-uber-fx:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore スコア
このスコアの理由 証拠の信頼度: 中作成できるもの
Migrate a Go service
Restructure manual application wiring into Fx providers, invokes, modules, and lifecycle hooks.
Standardize service modules
Define reusable HTTP, database, metrics, and worker modules with clear ownership and scoped decorators.
Test dependency graphs
Validate production wiring and replace real dependencies with fakes through fxtest utilities.
これらのプロンプトを試す
Explain how to wire my Go service with Uber Fx. Use these constructors: [constructors]. Identify the required Provide and Invoke calls.
Refactor this startup flow into Fx lifecycle hooks: [current flow]. Keep OnStart nonblocking and implement graceful shutdown with context cancellation.
Design Fx modules for these service areas: [areas]. Show provider ownership, scoped decorators, named dependencies, and value groups where appropriate.
Audit this Uber Fx composition root: [implementation]. Find missing providers, lifecycle hazards, annotation errors, unordered groups, and test gaps. Propose focused fixes.
ベストプラクティス
- Keep the composition root small and organize related providers inside named modules.
- Put side effects in lifecycle hooks and honor cancellation during startup and shutdown.
- Validate the production graph in tests and replace external dependencies with focused fakes.
回避
- Do not start blocking work inside constructors or synchronous OnStart hooks.
- Do not assume value groups preserve registration order.
- Do not hide required infrastructure behind optional dependencies.
よくある質問
When should I use Uber Fx?
When is raw Dig a better choice?
Does the skill run my application?
Can it help with graceful shutdown?
Can it help test an Fx application?
Does it choose application-specific dependencies?
開発者情報
作成者
samberライセンス
MIT
作者バージョン
v1.2.2
Skillstore リビジョン
r1
参照
2aa351cb09c29b7287d263bd8ea81e9bee3b2a61
メンテナンスの新しさ
2026/9/30
利用状況
0 ダウンロード · 0 閲覧
ファイル構成