sokrates-people-config

Run build_people_config.py with --repo pointing at a repository containing git-history.txt, or --landscape pointing at a landscape root. It writes config-people.json with merged identities and a config-people-for-review.json listing every merge for human verification.

Inflated counts usually come from one person committing under several e-mail addresses. This Skill resolves those identities into config-people.json entries with emailPatterns, so Sokrates collapses them into one person and reports accurate bus-factor and team-size numbers.

It applies seven confidence-rated rules: same e-mail, same normalized user name, GitHub noreply address forms, e-mail local part matching a GitHub login, same local part across domains, local parts derived from name patterns, and similar user names. Bots and generic names like admin are excluded.

No. Existing config-people.json entries are loaded first and seeded as certain merge groups, so hand-made entries, links, and images are preserved on every re-run. Rejected merges stay rejected because the tool never modifies existing entries.

Use medium in organizations where one login maps to one person across domains, since it additionally merges same-local-part and name-derived-address candidates. Avoid it for open-source portfolios where the same local part on different domains often belongs to different people.

The script falls back to reading contributor data from the repository's analysisResults inside _sokrates/reports/data/data.zip. Note that those contributors may already reflect a previous config-people.json merge, so git-history.txt is the preferred source.