Profile how a repo's maintainer works, then contribute in their idiom. Use when the user is about to write something that goes back to a repo they don't own: opening a PR, writing a commit for an upstream project, or asking to match a maintainer's conventions so a change gets merged. Do NOT use to understand an inherited codebase or find out why a convention exists, that is precedent, and do NOT use to build practice across several repos, that is canon.