go-onedrive

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.

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.

Generates performance and benchmark tests for the CLI and its underlying services. These tests measure execution time, memory usage, and throughput to ensure the application remains efficient under load.

Generates rapid smoke tests for the CLI. These tests are designed to run in seconds after a build or deployment to ensure that the application's most basic and vital functions are operational.

Generates idiomatic Go unit tests using the table-driven pattern and the testify assertion library. Use when adding new features, fixing bugs, or improving test coverage to ensure robust and maintainable code.

Helps in drafting, editing, and managing Architectural Decision Records (ADRs). Use when an architect-level decision needs to be formally documented, reviewed, or updated within the project's docs/adr/ directory.

Assists in creating standardized conventional commit messages. Use when committing changes to ensure consistent versioning and changelog generation.