Dotnet best practices vs System commandline CLI
Dotnet best practices is an open-source agent skill for developer tools. System commandline CLI is an open-source agent skill for developer tools.
- Dotnet best practices is best for review a c# class for missing xml documentation and naming issues.
- System commandline CLI is best for add a new subcommand with options to an existing .net cli.
- What it is
- Dotnet best practices is an open-source agent skill for developer tools.System commandline CLI is an open-source agent skill for developer tools.
- Best for
- Review a C# class for missing XML documentation and naming issuesAdd a new subcommand with options to an existing .NET CLI
- Kind
- SkillSkill
- Pricing
- Open sourceOpen source
- Platforms
- Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf, GooseClaude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf, Goose
- GitHub stars
- 41.3K41.3K
- Last commit
- Nov 2026Nov 2026
- License
- MITMIT
- Open source
- Good for
- Review a C# class for missing XML documentation and naming issues; Add dependency injection and null checks to a .NET service; Write MSTest unit tests with FluentAssertions and Moq for a handlerAdd a new subcommand with options to an existing .NET CLI; Create a command group that nests several related verbs; Add a global endpoint option with validation to the root command
What Dotnet best practices does
XML documentation guidance
Asks for XML comments on public types and members, including parameter and return descriptions.
Dependency injection rules
Covers constructor injection, null checks, service lifetimes and interface-based design.
Async and error handling
Guides use of async/await, ConfigureAwait, specific exceptions and structured logging.
Testing conventions
Specifies MSTest with FluentAssertions and Moq, AAA layout and null-parameter tests.
Configuration and localization
Recommends strongly typed settings with validation and ResourceManager-based messages.
Semantic Kernel guidance
Outlines kernel setup, model settings and structured output for AI operations in .NET.
What System commandline CLI does
Command base class pattern
Shows how to derive concrete commands from a shared abstract base built on System.CommandLine's Command type.
Options and arguments setup
Covers defining typed options with aliases and positional arguments, and reading their values in handlers.
Command groups and registration
Explains how parent commands register subcommands and how top-level commands attach to the root.
Global option validation
Describes defining shared options once, making them recursive, and validating endpoints and secrets at parse time.
Service injection rules
Keeps handlers thin by routing logic through interfaces resolved from dependency injection.
New command checklist
Provides a verification list covering naming, visibility, file placement, and handler signature for new commands.
Dotnet best practices vs System commandline CLI: questions
Is Dotnet best practices or System commandline CLI cheaper?
Both are open source. Compare current plans on each official site.
What is the difference between Dotnet best practices and System commandline CLI?
Dotnet best practices is an open-source agent skill for developer tools. System commandline CLI is an open-source agent skill for developer tools.
