Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

dotnet-explain

Estrelas2

Forks1

Atualizado27 de fevereiro de 2026 às 17:08

Answers questions about the .NET quality methodology — why tools are chosen, how thresholds work, what each dimension covers, and how hooks interact. Use when user asks "why this tool", "what does the quality gate do", "how are thresholds set", or any .NET methodology question.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

ondrasek

ondrasek/cc-plugins

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

name	dotnet-explain
description	Answers questions about the .NET quality methodology — why tools are chosen, how thresholds work, what each dimension covers, and how hooks interact. Use when user asks "why this tool", "what does the quality gate do", "how are thresholds set", or any .NET methodology question.
metadata	{"version":"1.0.0","author":"Ondrej (Ondra) Krajicek, me@ondrejkrajicek.com"}

.NET Explain

Read-only — does not modify any files.

Context Files

skills/shared/references/explain-pattern.md — shared answer format and behavior
skills/shared/references/methodology-framework.md — shared principles, hook architecture
skills/dotnet-setup/references/methodology.md — .NET-specific dimensions, rationale, adaptation rules
skills/dotnet-setup/references/analysis-checklist.md — how projects are analyzed

Example Questions

"Why Roslyn analyzers over external tools?" → Dimension 2. Roslyn analyzers run during dotnet build, integrate with IDEs, controlled via .editorconfig. No separate step needed.

"What's the coverage threshold?" → Dimension 1. 90% default; 70% for new projects; legacy: start at current.

"Should I use all 9 dimensions?" → Principles: incremental adoption. Start with testing + linting, add incrementally.

"Why Directory.Build.props?" → .NET-Specific Patterns. Centralizes MSBuild properties, avoids duplication across .csproj files.

"How does nullable reference types fit?" → Dimension 3. <Nullable>enable</Nullable> + AnalysisLevel: latest-Recommended.

"How do I disable a check?" → Each check has a [check:*] comment marker. Delete the run_check block.

Mais deste repositório

mesmo repositório

copilot-loop

ondrasek/cc-plugins

Iterate a feature branch to a clean Copilot review — stage/commit/push, open or update the PR, request a GitHub Copilot code review, wait for the review to land, address each comment with a code fix, push, re-request, and loop until Copilot returns no new comments. Use when user says "copilot review loop", "iterate with copilot", "copilot loop", "merge with copilot", "ship with copilot review", "auto-fix copilot comments", "loop until copilot is happy", or wants automated PR iteration driven by Copilot's feedback.

2026-05-012

vault-setup

ondrasek/cc-plugins

Analyzes a git-managed Obsidian vault and configures 7-dimension quality methodology including hooks, quality gate, CLAUDE.md, and GitHub Actions workflows. Use when user says "set up vault quality", "configure obsidian", "vault setup", "obsidian quality", or wants to apply quality standards to an Obsidian vault.

2026-04-052

develop

ondrasek/cc-plugins

Bridge GitHub issues to development workflow — create branches, start work, check status. Use when user says "start working on issue

2026-03-192

dotnet-setup

ondrasek/cc-plugins

Analyzes a .NET/C# project and configures 9-dimension quality methodology including hooks, CI, and tool configs. Use when user says "set up quality tools", "configure analyzers", "add CI pipeline", "dotnet quality", or wants to apply coding standards to a .NET project.

2026-03-022

nvim-lua-setup

ondrasek/cc-plugins

Analyzes a Neovim Lua plugin and configures 9-dimension quality methodology including hooks, CI, and tool configs. Use when user says "set up quality tools", "configure linting", "add CI pipeline", "neovim lua quality", or wants to apply coding standards to a Neovim Lua plugin.

2026-03-022

python-setup

ondrasek/cc-plugins

Analyzes a Python project and configures 9-dimension quality methodology including hooks, CI, and tool configs. Use when user says "set up quality tools", "configure linting", "add CI pipeline", "python quality", or wants to apply coding standards to a Python project.

2026-03-022

name	dotnet-explain
description	Answers questions about the .NET quality methodology — why tools are chosen, how thresholds work, what each dimension covers, and how hooks interact. Use when user asks "why this tool", "what does the quality gate do", "how are thresholds set", or any .NET methodology question.
metadata	{"version":"1.0.0","author":"Ondrej (Ondra) Krajicek, me@ondrejkrajicek.com"}

.NET Explain

Read-only — does not modify any files.

Context Files

skills/shared/references/explain-pattern.md — shared answer format and behavior
skills/shared/references/methodology-framework.md — shared principles, hook architecture
skills/dotnet-setup/references/methodology.md — .NET-specific dimensions, rationale, adaptation rules
skills/dotnet-setup/references/analysis-checklist.md — how projects are analyzed

Example Questions

"Why Roslyn analyzers over external tools?" → Dimension 2. Roslyn analyzers run during dotnet build, integrate with IDEs, controlled via .editorconfig. No separate step needed.

"What's the coverage threshold?" → Dimension 1. 90% default; 70% for new projects; legacy: start at current.

"Should I use all 9 dimensions?" → Principles: incremental adoption. Start with testing + linting, add incrementally.

"Why Directory.Build.props?" → .NET-Specific Patterns. Centralizes MSBuild properties, avoids duplication across .csproj files.

"How does nullable reference types fit?" → Dimension 3. <Nullable>enable</Nullable> + AnalysisLevel: latest-Recommended.

"How do I disable a check?" → Each check has a [check:*] comment marker. Delete the run_check block.