health-check

Convert MCP diagnostic outputs into letter-graded health reports for .NET projects.

Updated Apr 27, 2026
One-click install
npx skills add https://github.com/shahdanish/vibepos --skill health-check-shahdanish
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: health-check
Source: https://github.com/shahdanish/vibepos/tree/main/skills/health-check
Command: npx skills add https://github.com/shahdanish/vibepos --skill health-check-shahdanish

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you objectively assess the health of a .NET repository using evidence-based MCP tools, turning build, quality, architecture, tests, dead code, API design, security, and documentation into a prioritized, grade-driven action plan.

Core Features & Use Cases

  • 8-dimension health assessment with letter grades (A–F) for build health, code quality, architecture, test coverage, dead code, API surface, security posture, and documentation quality.
  • Data-driven justification that ties each grade to measurable findings (e.g., warnings/errors, anti-pattern counts, circular dependency detection, test-class presence).
  • Actionable recommendations that prioritize concrete fixes based on the detected evidence rather than vague suggestions.

Quick Start

Run a full health assessment by asking: "Do a health check of this repository and return an 8-dimension A–F report with prioritized recommendations."

Frequently Asked Questions about health-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a .NET codebase health assessment to get an A–F grade report?

Run a .NET codebase health assessment by executing MCP diagnostic tools across eight dimensions, which converts static analysis and test coverage findings into an evidence-based A–F report card. The resulting structured report includes prioritized fixes tied to measurable data points.

What dimensions are evaluated in a .NET repository architecture audit?

A .NET repository architecture audit evaluates eight dimensions: build health, code quality, architecture, test coverage, dead code, API exposure, security posture, and documentation quality. Each dimension receives an evidence-based letter grade based on defined thresholds and measurable findings.

Can I use static analysis to prioritize technical debt in a .NET project?

Yes, you can use static analysis to prioritize technical debt in a .NET project by grading anti-pattern counts, circular dependencies, and dead code against defined thresholds. This generates a prioritized, grade-driven action plan with concrete fixes.

Does a .NET code quality review require specific MCP tools installed?

Yes, a .NET code quality review requires MCP diagnostic tools to gather evidence for grading. The Skill converts MCP tool outputs into letter grades, meaning you must run MCP diagnostics for each dimension to produce the structured report card.

When should I do a codebase review for a .NET project release?

You should do a codebase review for a .NET project release when using pre-release quality gates to assess technical debt. The health check provides evidence-based grades across security posture and test coverage to justify deployment readiness.