who-is-actor

Analyzes Git commit history to profile developers across six behavioral dimensions.

39|1|Updated Jul 2, 2026
One-click install
npx skills add https://github.com/HKU-MMLab/UniClawBench --skill who-is-actor-hku-mmlab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: who-is-actor
Source: https://github.com/HKU-MMLab/UniClawBench/tree/main/injection/101_skill_usage/task_101_27_pr_triage/skills/who-is-actor
Command: npx skills add https://github.com/HKU-MMLab/UniClawBench --skill who-is-actor-hku-mmlab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Understanding how each developer actually works inside a Git repository normally requires installing analytics tools or manually digging through git log output. This Skill turns raw commit history into a structured, data-driven profile of every contributor without installing any packages or running custom scripts. ## Core Features & Use Cases - Six-Dimension Developer Profiling: Scores each contributor on commit habits, work habits, development efficiency, code style, code quality, and an engagement index, using only native read-only git commands and standard Unix text utilities. - Security-Hardened Execution: Enforces a strict command whitelist, input validation against injection attacks, dry-run preview mode, email privacy protection, and automatic redaction of secrets before any data reaches the AI model. - Team-Level Reporting: Produces a Markdown report with a summary table, per-developer radar scores and commentary, team cross-comparison, and bus-factor risk alerts. - Use Case: A tech lead asks "analyze the repository at /path/to/my-project and compare Alice and Bob's development efficiency" and receives a full report showing commit frequency, churn rate, late-night coding ratios, and actionable improvement suggestions for each person. ## Quick Start Ask the agent to analyze the Git repository at your chosen absolute path and generate a developer profile report for all contributors.

Frequently Asked Questions about who-is-actor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I analyze developer commit habits in a Git repository?▼

Provide the absolute path to your Git repository and ask for a developer profile report. The skill runs read-only git log and shortlog commands, then produces six-dimension scores, commentary, and a team comparison table for every contributor.

What metrics does a Git developer profiling report include?▼

The report covers commit frequency, lines added and deleted, weekend and late-night ratios, bug-fix percentage, code churn rate, Conventional Commits compliance, an engagement index, and a weighted overall score per developer.

Does this Git analysis require installing Python or Node packages?▼

No packages are installed. It relies only on the git binary plus standard Unix text tools (cut, sort, uniq, awk, grep, sed, wc, head) that are pre-installed on macOS and Linux; Windows users need Git Bash or WSL.

Is it safe to run Git log analysis on a private repository?▼

Yes, with precautions. Only whitelisted read-only git commands are allowed, all inputs are validated against injection patterns, emails are never collected, and commit messages are reduced to aggregated metrics with automatic secret redaction. A dry-run mode lets you review every command first.

Can the engagement index be used for performance reviews?▼

No. The documentation explicitly prohibits using the engagement index for performance reviews, layoffs, or compensation decisions, because Git commits do not capture design work, code reviews, mentoring, or other non-code contributions.