メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
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.
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 | cli-design |
| description | 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. |
[TODO: 1-2 sentences explaining what this skill enables]
[TODO: Choose the structure that best fits this skill's purpose. Common patterns:
1. Workflow-Based (best for sequential processes)
2. Task-Based (best for tool collections)
3. Reference/Guidelines (best for standards or specifications)
4. Capabilities-Based (best for integrated systems)
Patterns can be mixed and matched as needed. Most skills combine patterns (e.g., start with task-based, add workflow for complex operations).
Delete this entire "Structuring This Skill" section when done - it's just guidance.]
[TODO: Add content here. See examples in existing skills:
This skill includes example resource directories that demonstrate how to organize different types of bundled resources:
Executable code that can be run directly to perform specific operations.
Examples from other skills:
Appropriate for: Node.cjs scripts (cjs), shell scripts, or any executable code that performs automation, data processing, or specific operations.
Note: Scripts may be executed without loading into context, but can still be read by Gemini CLI for patching or environment adjustments.
Documentation and reference material intended to be loaded into context to inform Gemini CLI's process and thinking.
Examples from other skills:
Appropriate for: In-depth documentation, API references, database schemas, comprehensive guides, or any detailed information that Gemini CLI should reference while working.
Files not intended to be loaded into context, but rather used within the output Gemini CLI produces.
Examples from other skills:
Appropriate for: Templates, boilerplate code, document templates, images, icons, fonts, or any files meant to be copied or used in the final output.
Any unneeded directories can be deleted. Not every skill requires all three types of resources.
