Inspect repository configuration

I need to verify repository configuration that affects merges and hooks. Show the current repository-level and local user configuration for my project, including core.autocrlf, receive.denyCurrentBranch, and the hooksPath setting. List the values and note any that deviate from our team standards. Ladder":"L1"

Before I hand this to the release lead, make the configuration easy to audit. Summarize which config keys affect developer experience, surface anything that could break cross-platform commits (autocrlf, safecrlf), and flag any global config that would override repo behavior. Provide a one-paragraph recommendation for each finding. Ladder":"L2"

I pulled the repo config and hooksPath points to /opt/shared/hooks, and I am unsure if that is intentional. I fear local hook behavior will differ between machines and I cannot tell whether the shared path is available to everyone or a leftover from an old CI. What is the likely consequence and the best immediate check to confirm if developers will see those hooks? Ladder":"L5"

We keep getting subtle failures because some clones inherit different core settings and hooks references. The pattern over many incidents is ad-hoc fixes pushed as global config changes on individual machines. Recommend one change to how we store and enforce repository configuration and one onboarding habit that will prevent this drift. Ladder":"L6"