How do I install the Loc Change Table skill?

Run npx skillmds@latest add lkshrk/loc-change-table in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Loc Change Table safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Loc Change Table?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Loc Change Table free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Loc Change Table?

lkshrk (@lkshrk) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Loc Change Table by lkshrk — Agent Skill

Name: Loc Change Table
Author: lkshrk

Loc Change Table

Count line changes in one folder and all subdirectories since a given date, grouped by git repository and file category. Use when the user asks for LOC changes, line changes, churn, diff stats, changed lines, or repo-by-category tables since a date.

lkshrk Updated Sep 17, 2026

File contents

LOC Change Table

Use this skill when the user wants a repo-by-category table of line changes under a folder since a date.

How to run

The bundled script is the single source of truth. Run it and present its output verbatim. Do not hand-compute counts, and do not substitute ad-hoc git log/git diff one-liners — they count differently and produce inconsistent results.

Resolve the inputs:
- Folder: use the user's path, or the current working directory if none is given.
- Date: required. If the user did not give one, ask. Accept any git-compatible form, such as 2026-06-01, last Friday, or 2 weeks ago.

Run:

python3 scripts/loc_change_table.py <folder> --since <date>

Present the Markdown table the script prints, then relay its trailing notes (hidden repos, empty-tree warnings, skipped repos). Do not drop the notes — the empty-tree warning is how a wrong date is caught.

Flags

--include-uncommitted — also count working-tree changes (only when the user asks for uncommitted work).
--include-binary — count each changed binary file as 1 line.
--show-empty — also list repos with zero changes (hidden by default).

Behavior

Counts added + deleted per file from git diff --numstat, diffing HEAD against the last commit before --since.
If no commit predates the date, the repo is diffed against the empty tree (full history) and flagged in a note — surface that note so inflated totals are visible.
Each nested git repository is its own row; repos with no changes are hidden; rows are sorted by total descending.
Repos with no commits or git errors are reported under "Skipped".

Categories

Script defaults (precedence: generated, tests, docs, config, frontend, backend, other):

frontend: .js/.jsx/.ts/.tsx/.svelte/.vue/.css/.scss/.sass/.less/.html
backend: .py/.go/.rs/.java/.kt/.cs/.rb/.php
tests: paths with test/tests/spec/specs/__tests__, or .test.* / .spec.* files
config: .json/.yaml/.yml/.toml/.ini/.env, Dockerfiles, Makefiles, lockfiles, CI folders
docs: .md/.mdx/.rst/.txt, docs/, README, CHANGELOG
generated: generated/gen/dist/build, coverage, snapshots, lockfiles
other: anything else

---name: loc-change-tabledescription: Count line changes in one folder and all subdirectories since a given date, grouped by git repository and file category. Use when the user asks for LOC changes, line changes, churn, diff stats, changed lines, or repo-by-category tables since a date.---# LOC Change TableUse this skill when the user wants a repo-by-category table of line changes under a folder since a date.## How to runThe bundled script is the single source of truth. Run it and present its output verbatim. Do not hand-compute counts, and do not substitute ad-hoc `git log`/`git diff` one-liners — they count differently and produce inconsistent results.1. Resolve the inputs: - Folder: use the user's path, or the current working directory if none is given. - Date: required. If the user did not give one, ask. Accept any `git`-compatible form, such as `2026-06-01`, `last Friday`, or `2 weeks ago`.2. Run: ```bash python3 scripts/loc_change_table.py <folder> --since <date> ```3. Present the Markdown table the script prints, then relay its trailing notes (hidden repos, empty-tree warnings, skipped repos). Do not drop the notes — the empty-tree warning is how a wrong date is caught.### Flags- `--include-uncommitted` — also count working-tree changes (only when the user asks for uncommitted work).- `--include-binary` — count each changed binary file as 1 line.- `--show-empty` — also list repos with zero changes (hidden by default).## Behavior- Counts `added + deleted` per file from `git diff --numstat`, diffing `HEAD` against the last commit before `--since`.- If no commit predates the date, the repo is diffed against the empty tree (full history) and flagged in a note — surface that note so inflated totals are visible.- Each nested git repository is its own row; repos with no changes are hidden; rows are sorted by total descending.- Repos with no commits or git errors are reported under "Skipped".## CategoriesScript defaults (precedence: `generated`, `tests`, `docs`, `config`, `frontend`, `backend`, `other`):- `frontend`: `.js/.jsx/.ts/.tsx/.svelte/.vue/.css/.scss/.sass/.less/.html`- `backend`: `.py/.go/.rs/.java/.kt/.cs/.rb/.php`- `tests`: paths with `test/tests/spec/specs/__tests__`, or `.test.*` / `.spec.*` files- `config`: `.json/.yaml/.yml/.toml/.ini/.env`, Dockerfiles, Makefiles, lockfiles, CI folders- `docs`: `.md/.mdx/.rst/.txt`, `docs/`, `README`, `CHANGELOG`- `generated`: `generated/gen/dist/build`, coverage, snapshots, lockfiles- `other`: anything else

Frequently asked questions