メニュー
Masterful Go documentation generator. Use when adding or improving GoDoc for packages, structs, methods, constants, and variables. Prioritizes high-signal, idiomatic comments following Effective Go and Go Code Review Comments philosophies.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
TODO: Complete and informative explanation of what the skill does and when to use it. Include WHEN to use this skill - specific scenarios, file types, or tasks that trigger it.
Generates Acceptance tests using BDD principles. These tests use Gherkin (Given/When/Then) and the `godog` framework to verify that the application satisfies high-level user requirements in a readable format.
Facilitates the creation and design of specialized sub-agents. Use when you need to define a new agent with proper frontmatter (tools, model, temperature, max_turns), role, mandate, and guidelines.
Generates End-to-End (E2E) tests for the CLI. These tests execute the compiled `odc` binary against a controlled environment (local files or mock server) to validate the entire application stack from CLI arguments to output.
Generates functional tests for CLI features. These tests verify complete business flows within the application boundary, mocking external I/O like the Microsoft Graph API but exercising multiple internal services together.
Generates integration tests for CLI commands, focusing on Cobra command wiring, flag parsing, and Dependency Injection (DI) integration. Use when testing how components work together within the CLI lifecycle.
| name | godoc-writer |
| description | Masterful Go documentation generator. Use when adding or improving GoDoc for packages, structs, methods, constants, and variables. Prioritizes high-signal, idiomatic comments following Effective Go and Go Code Review Comments philosophies. |
The godoc-writer skill transforms bare or verbose Go code into a masterfully documented API. It focuses on providing essential context—the "why" and "how"—while omitting redundant information that is already evident from the code itself.
Ensure every package has a summary. Use a doc.go file for complex packages.
// Package name ...Focus on the purpose and concurrency safety.
// Name [purpose/coordination]. [Concurrency details].Focus on behavior, side effects, and error conditions.
// Name [behavior/returns]. [Side effects]. [Error conditions].