This skill should be used ONLY when the user EXPLICITLY and UNAMBIGUOUSLY requests a Git repository commit-history analysis that produces aggregate collaboration-pattern metrics (commit cadence, churn, rework signals, conventional-commit compliance, bus-factor risk).
The skill is scoped to repository-level technical analysis. It is NOT a performance-management, HR, ranking, or personnel-evaluation tool, and agents MUST refuse to use its output for those purposes. Any developer display names appearing in output exist solely to attribute Git commit records, not to render judgments about individuals.
Activation requires an explicit, opt-in user request that BOTH (a) states a clear analyze-this-Git-repository intent AND (b) supplies a concrete repository path (or unambiguous repo reference). Generic conversational mentions of "analyze repository", "profile developers", "commit habits", "developer report card", "code quality", "team efficiency", "work habits", "engagement", "代码分析", "研发效率", "开发者画像", "提交习惯", "工作习惯",
2026-06-02