mcaf-dotnet-cloc

Analyze .NET repositories for line counts and branch comparisons using cloc.

4|Updated Mar 6, 2026

Search Tags:#codebase analysis #code metrics #line count #.net #cloc #ci

Ready to run

npx skills add https://github.com/managedcode/MCPGateway --skill mcaf-dotnet-cloc

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: mcaf-dotnet-cloc
Source: https://github.com/managedcode/MCPGateway/tree/main/.codex/skills/mcaf-dotnet-cloc
Command: npx skills add https://github.com/managedcode/MCPGateway --skill mcaf-dotnet-cloc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides detailed line-count, language-mix, and branch-to-branch statistics for .NET repositories, enabling precise code-size reporting and analysis.

Core Features & Use Cases

Codebase Metrics: Generates metrics for C# and other relevant file types in .NET solutions.
Branch Comparison: Compares code size differences between Git branches.
Use Case: Use this Skill to track the growth of your C# codebase over time or to quantify the impact of a refactoring by comparing code metrics before and after the changes.

Quick Start

Use the mcaf-dotnet-cloc skill to get a C# code count for the current repository.

Frequently Asked Questions about mcaf-dotnet-cloc

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

FAQPage Schema

How do I count lines of code in a .NET repository?▼

You can count lines of code in a .NET repository by analyzing your source files to generate detailed line-count and language-mix metrics. This Skill uses the cloc tool to provide repeatable code-size reporting for C# and other relevant file types.

Can I compare code size differences between Git branches in a .NET project?▼

Yes, you can compare code size differences between Git branches in a .NET project. This Skill provides branch-to-branch statistics to help you quantify the impact of a refactoring or track codebase growth before and after changes.

What is the best way to track C# codebase growth over time in CI?▼

The best way to track C# codebase growth over time in CI is by using repeatable code-size reporting tools. This Skill supports local workflows and CI pipelines to generate consistent line-count and language-mix metrics for your repositories.

Does the line count analysis support file types besides C# in .NET solutions?▼

Yes, the line count analysis supports file types besides C# in .NET solutions. It generates metrics for C# and other relevant file types found in your repository, providing a comprehensive language-mix breakdown for your codebase.

Do I need a Git checkout to analyze .NET code composition?▼

You need a repository with .NET source files or a Git checkout to analyze .NET code composition. This environment is required to execute the line-count analysis and generate accurate branch-to-branch statistics if comparing branches.

How do I limit the scope of a codebase analysis to specific directories?▼

You can limit the scope of a codebase analysis to specific directories by using explicit include and exclude rules. This allows you to execute bounded scope commands and generate line-count metrics only for the targeted source files.