New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Cloc

by managedcode in managedcode/dotnet-skills

Use the open-source free cloc tool for line-count, language-mix, and diff statistics in .NET repositories.

MITAuto-check: notesAgent Workflows

Install Cloc

skills CLI
$ npx skills add managedcode/dotnet-skills --skill cloc -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install managedcode/dotnet-skills cloc --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/managedcode/dotnet-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/catalog/Tools/cloc/skills/cloc .claude/skills/cloc && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
cloc
GitHub stars
486
Token cost
~1.5k tokens
SKILL.md length
734 words
Files
5 (incl. references)
Skills in repo
81
Repo updated
First seen
Licence
MIT

At a glance

Use the open-source free cloc tool for line-count, language-mix, and diff statistics in .NET repositories.

  • Works in 3 steps: Read the nearest AGENTS.md and confirm… → Run this skill's Workflow through the… → Return the Required Result Format with…
  • : repeatable LOC reports
  • SKILL.md covers Trigger On, Value, Do Not Use For and Inputs, plus 8 more sections
  • Calls brew, apt and yum

What it does

Cloc is an agent skill from managedcode/dotnet-skills. Use the open-source free cloc tool for line-count, language-mix, and diff statistics in .NET repositories. USE FOR: repeatable LOC reports; language-mix or branch-diff statistics; codebase size and solution-composition measurements. DO NOT USE FOR: judging developer productivity from raw LOC; replacing behavioral verification, architecture review, or complexity analysis. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `manifest.json`, `references/cloc.md` and `references/commands.md`). Compatibility notes: Requires a repository with .NET source files or a Git checkout; respects the repo's AGENTS.md commands first.

It sits in Agent Workflows, covering Software architecture, Statistics and Codebase knowledge for agents. It works with .NET, Git and C#. The repository describes itself as: Installable .NET skill catalog and CLI for Codex, Claude Code, GitHub Copilot, and Gemini. The licence is MIT.

When your agent uses it

  • : repeatable LOC reports
  • Branch-diff statistics
  • Codebase size and solution-composition measurements
  • : judging developer productivity from raw LOC

Example prompts

  • “/cloc”

Requirements

  • Node.js
  • Docker
  • Compatibility (from SKILL.md): Requires a repository with .NET source files or a Git checkout; respects the repo's `AGENTS.md` commands first.

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. Read the nearest AGENTS.md and confirm scope and constraints.
  2. Run this skill's Workflow through the Ralph Loop until outcomes are acceptable.
  3. Return the Required Result Format with concrete artifacts and verification evidence.

What it can do on your machine

Read from SKILL.md and the folder at commit 535dd55. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • brew
    • apt
    • yum
    • dnf
    • npm
    • choco
    • docker

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npm and docker, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Requires a repository with .NET source files or a Git checkout; respects the repo's `AGENTS.md` commands first.

    From compatibility in the SKILL.md frontmatter.

Context cost

Cloc loads about 1.5k tokens when it runs, and up to ~4.4k if it reads all its reference files. Until then it costs about 131 tokens; SKILL.md has 734 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~131
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~4.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteRuns commands with sudoSKILL.md:76
    - Debian or Ubuntu: `sudo apt install cloc`
  • NoteRuns commands with sudoSKILL.md:77
    - Red Hat or older Fedora family: `sudo yum install cloc`
  • NoteRuns commands with sudoSKILL.md:78
    - Fedora or newer Red Hat family: `sudo dnf install cloc`

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from managedcode/dotnet-skills at commit 535dd55, republished under its MIT licence (© managedcode). 734 words, ~1,539 tokens.

Download SKILL.mdSave it as .claude/skills/cloc/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
cloc
description
Use the open-source free `cloc` tool for line-count, language-mix, and diff statistics in .NET repositories. USE FOR: repeatable LOC reports; language-mix or branch-diff statistics; codebase size and solution-composition measurements. DO NOT USE FOR: judging developer productivity from raw LOC; replacing behavioral verification, architecture review, or complexity analysis. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.
compatibility
Requires a repository with .NET source files or a Git checkout; respects the repo's `AGENTS.md` commands first.

CLOC for .NET Repositories

Trigger On

  • the repo wants cloc
  • the team needs repeatable LOC, language, or branch diff statistics for a .NET repo
  • the user asks about C# codebase size, solution composition, or code-count deltas between refs

Value

  • produce a concrete project delta: code, docs, config, tests, CI, or review artifact
  • reduce ambiguity through explicit planning, verification, and final validation skills
  • leave reusable project context so future tasks are faster and safer

Do Not Use For

  • judging developer productivity from raw LOC
  • replacing behavioral verification, architecture review, or complexity analysis
  • counting generated or vendored files without an explicit reason

Inputs

  • the nearest AGENTS.md
  • target repository, solution, project, or subtree
  • the question being answered: footprint, composition, diff, or trend

Quick Start

  1. Read the nearest AGENTS.md and confirm scope and constraints.
  2. Run this skill's Workflow through the Ralph Loop until outcomes are acceptable.
  3. Return the Required Result Format with concrete artifacts and verification evidence.

Workflow

  1. Choose the counting mode deliberately:
    • --vcs=git for repo-respecting counts
    • path-based counting for bounded folders
    • --git --diff BASE HEAD for change deltas
  2. Prefer .NET-relevant views first:
    • C# footprint
    • test versus production footprint
    • solution language mix such as C#, Razor, XML, JSON, YAML, and MSBuild files
  3. Exclude noise before trusting the numbers:
    • bin
    • obj
    • .git
    • vendored or generated folders when they are not part of the decision
  4. Use machine-readable output when the numbers feed docs, CI, or follow-up automation:
    • --json
    • --csv
    • --yaml
    • --md
  5. Treat cloc as a sizing and comparison tool, not as evidence that the design is good.
  6. When using diff mode, compare named refs that match the review question:
    • origin/main..HEAD
    • release branch versus main
    • before and after a refactor
  7. After any code cleanup based on cloc findings, run the repo's normal quality pass.

Bootstrap When Missing

If cloc is not available yet:

  1. Detect current state:
    • command -v cloc
    • cloc --version
    • perl --version
  2. Choose the install path deliberately:
    • macOS with Homebrew: brew install cloc
    • Debian or Ubuntu: sudo apt install cloc
    • Red Hat or older Fedora family: sudo yum install cloc
    • Fedora or newer Red Hat family: sudo dnf install cloc
    • npm fallback: npm install -g cloc
    • Windows with Chocolatey: choco install cloc
    • Windows with Scoop: scoop install cloc
    • Docker fallback: docker run --rm -v $PWD:/tmp aldanial/cloc .
  3. If package-manager builds are not acceptable, install from the latest upstream release or source and verify with cloc --version.
  4. Record exact counting commands in AGENTS.md, for example:
    • cloc --vcs=git --include-lang="C#,MSBuild,JSON,XML,YAML"
    • cloc --by-file --vcs=git --include-lang="C#"
    • cloc --git --diff origin/main HEAD --include-lang="C#"
  5. Run one bounded command and return status: configured or status: improved.
  6. If the repo intentionally uses another code-count tool and does not want cloc, return status: not_applicable.
Show full SKILL.md (281 more words)Show less

Deliver

  • repeatable LOC and language-mix reporting for .NET repos
  • explicit include and exclude rules
  • branch-diff or bounded-scope commands that answer a concrete engineering question

Validate

  • counts match the intended source boundary instead of including build output noise
  • command choice matches the reporting question
  • any automation or docs that consume the numbers can rerun the same command
  • cloc is used as context, not as a substitute for tests or design review

Ralph Loop

Use the Ralph Loop for every task, including docs, architecture, testing, and tooling work.

  1. Plan first (mandatory):
    • analyze current state
    • define target outcome, constraints, and risks
    • write a detailed execution plan
    • list final validation skills to run at the end, with order and reason
  2. Execute one planned step and produce a concrete delta.
  3. Review the result and capture findings with actionable next fixes.
  4. Apply fixes in small batches and rerun the relevant checks or review steps.
  5. Update the plan after each iteration.
  6. Repeat until outcomes are acceptable or only explicit exceptions remain.
  7. If a dependency is missing, bootstrap it or return status: not_applicable with explicit reason and fallback path.
Required Result Format
  • status: complete | clean | improved | configured | not_applicable | blocked
  • plan: concise plan and current iteration step
  • actions_taken: concrete changes made
  • validation_skills: final skills run, or skipped with reasons
  • verification: commands, checks, or review evidence summary
  • remaining: top unresolved items or none

For setup-only requests with no execution, return status: configured and exact next commands.

Load References

Example Requests

  • "Add cloc reporting to this .NET repo."
  • "Compare code size between main and this branch."
  • "Count C# versus test footprint in this solution."
  • "Give me a machine-readable line-count report for CI."

© managedcode, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 4 other files (references) in catalog/Tools/cloc/skills/cloc of managedcode/dotnet-skills.

  • SKILL.md
  • manifest.json
  • references/cloc.md
  • references/commands.md
  • references/examples.md

Open the folder on GitHubat commit 535dd55

Compare with similar skills

Cloc next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Cloc compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Cloc this skillmanagedcode/dotnet-skills486—~1.5kAutomated safety check: NotesMIT
Mcaf Dotnet Clocmanagedcode/Storage138—~1.4kAutomated safety check: NotesMIT
GitVersion .NET DevelopmentGitTools/GitVersion3.1k—~1.7kAutomated safety check: PassMIT
Akka.Hosting Actor PatternsAaronontheweb/dotnet-skills1.2k1 repos~5kAutomated safety check: PassMIT
Akka.NET Best PracticesAaronontheweb/dotnet-skills1.2k1 repos~3.3kAutomated safety check: PassMIT
Git HooksProrise-cool/Claude-Code-Multi-Agent305—~3.6kAutomated safety check: NotesNone

Similar skills

  • Mcaf Dotnet Cloc

    managedcode/Storage

    Use the open-source free cloc tool for line-count, language-mix, and diff statistics in .NET repositories.

    138 GitHub stars~1.4k tokensUpdated yesterday
    Agent WorkflowsAuto-check: notes

  • GitVersion .NET Development

    GitTools/GitVersion

    Gives repository-specific .NET guidance for GitVersion: build and test commands, central package management, project layout and coding conventions.

    3.1k GitHub stars~1.7k tokensUpdated today
    DevelopmentAuto-check passed

  • Akka.Hosting Actor Patterns

    Aaronontheweb/dotnet-skills

    Shows how to build entity actors with Akka.Hosting so the same code runs in local unit tests and in a sharded cluster in production.

    1.2k GitHub starsUsed in 1 repo~5k tokens
    DevelopmentAuto-check passed

  • Akka.NET Best Practices

    Aaronontheweb/dotnet-skills

    Guidance for Akka.NET actor systems covering EventStream versus DistributedPubSub, supervision, Props versus DependencyResolver, work distribution and testable cluster code.

    1.2k GitHub starsUsed in 1 repo~3.3k tokens
    DevelopmentAuto-check passed

  • Git Hooks

    Prorise-cool/Claude-Code-Multi-Agent

    Central authority on git hook implementations, modern best practices, and tooling for .NET/C, JavaScript/TypeScript, Python, and polyglot repositories.

    305 GitHub stars~3.6k tokensUpdated 22 days ago
    DevelopmentAuto-check: notes

  • Precheck

    ayutaz/piper-plus

    PR 作成前の lint + format + test 一括実行。引数で scope (python/rust/cs/go/js/cpp/all) を指定可能。未指定なら git diff から自動判定。

    220 GitHub stars~647 tokensUpdated today
    DevelopmentAuto-check passed

More from managedcode/dotnet-skills

All 81 skills in this repo

  • Analyzer Config

    managedcode/dotnet-skills

    Use a repo-root .editorconfig to configure free .NET analyzer and style rules.

    486 GitHub stars~1.3k tokensUpdated yesterday
    Auto-check passed

  • Archunitnet

    managedcode/dotnet-skills

    Use the open-source free ArchUnitNET library for architecture rules in .NET tests.

    486 GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed

  • Aspire

    managedcode/dotnet-skills

    Build, upgrade, and operate Aspire 13.5.x C or TypeScript application hosts with the current CLI, AppHost, ServiceDefaults, integrations, dashboard, testing, MCP, and deployment patterns for…

    486 GitHub stars~3.6k tokensUpdated yesterday
    Auto-check passed

  • Aspnet Core

    managedcode/dotnet-skills

    Build, debug, modernize, or review ASP.NET Core applications with correct hosting, middleware, security, configuration, logging, and deployment patterns on current .NET.

    486 GitHub stars~2.1k tokensUpdated yesterday
    Auto-check passed

  • Asynkron Profiler

    managedcode/dotnet-skills

    Use the open-source free Asynkron.Profiler dotnet tool for CLI-first CPU, allocation, exception, contention, and heap profiling of .NET commands or existing trace artifacts.

    486 GitHub stars~1.7k tokensUpdated yesterday
    Auto-check passed

  • Azure Functions

    managedcode/dotnet-skills

    Build, review, or migrate Azure Functions in .NET with correct execution model, isolated worker setup, bindings, DI, and Durable Functions patterns.

    486 GitHub stars~2.6k tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Cloc

What does Cloc do?

Use the open-source free cloc tool for line-count, language-mix, and diff statistics in .NET repositories. Cloc is an agent skill from managedcode/dotnet-skills.NET repositories.

When should I use Cloc?

Cloc fits situations like: : repeatable LOC reports; branch-diff statistics; codebase size and solution-composition measurements; : judging developer productivity from raw LOC.

How do I install Cloc in Claude Code?

Run `npx skills add managedcode/dotnet-skills --skill cloc -a claude-code`. Or copy the skill folder (catalog/Tools/cloc/skills/cloc in managedcode/dotnet-skills) into .claude/skills/cloc in your project. Claude Code loads it when a task matches its description.

How do I install Cloc in Codex?

Run `npx skills add managedcode/dotnet-skills --skill cloc -a codex`. Or copy the skill folder (catalog/Tools/cloc/skills/cloc in managedcode/dotnet-skills) into .agents/skills/cloc in your project. Codex loads it when a task matches its description.

Can I use Cloc in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add managedcode/dotnet-skills --skill cloc -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cloc, .gemini/skills/cloc, .github/skills/cloc and .opencode/skills/cloc in your project.

What does Cloc need to run?

Going by SKILL.md and its folder, Cloc needs the command-line tools its instructions call (brew, apt, yum, dnf, npm and choco). Our summary lists: Node.js; Docker. Compatibility (from SKILL.md): Requires a repository with .NET source files or a Git checkout; respects the repo's `AGENTS.md` commands first..

Does Cloc access the network?

SKILL.md contains no URLs. Its commands use npm and docker, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Cloc safe to install?

Our automated static check of SKILL.md found notes only (runs commands with sudo), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Cloc use?

Cloc is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Cloc use?

About 1.5k tokens (SKILL.md is roughly 6.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.8k tokens, read only when the agent opens those files.

What are the alternatives to Cloc?

Skills that share tags, products or a category with Cloc: Mcaf Dotnet Cloc (managedcode/Storage, 138 stars), GitVersion .NET Development (GitTools/GitVersion, 3.1k stars), Akka.Hosting Actor Patterns (Aaronontheweb/dotnet-skills, 1.2k stars) and Akka.NET Best Practices (Aaronontheweb/dotnet-skills, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Cloc?

managedcode (a GitHub organization) maintains it in managedcode/dotnet-skills, which has 486 GitHub stars. The repository holds 81 skills in this directory. The repository was last updated on October 7, 2026.

Source: managedcode/dotnet-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.