Project Personality

Read a repository's habits and give it a personality type — but every trait must trace to a number you measured in this session. The point is not to be cute. It is to make structural facts memorable enough that someone actually acts on them.

Why evidence first

People ignore dashboards and remember stories. A label like "this repo is a hoarder" only helps if the reader can verify it in thirty seconds. So the order is always: measure → name → point at the proof. A personality claim with no number behind it is a horoscope, and users can smell the difference.

Workflow

1. Measure

Run these in the project root. Adapt to the platform — on Windows without a POSIX shell use git ls-files and Get-ChildItem -Recurse. What matters is that you actually ran them, not which syntax you used.

# size and shape
git ls-files | wc -l
git ls-files | sed 's/.*\.//' | sort | uniq -c | sort -rn | head -10