Agent skill · data analytics · bighardperson

code-analysis

This skill should be used when the user needs to analyze Git repositories, compare developer commit patterns, work habits, development efficiency, code style, code quality, and slacking behaviors. It generates honest, direct developer evaluations with scores, grades, strengths, weaknesses, and actionable suggestions. Trigger phrases include "analyze code", "analyze repository", "compare developers", "code quality report", "commit patterns", "developer efficiency", "developer evaluation", "slacking index", "摸鱼指数", "工作习惯分析", "代码分析", "研发效率", "代码质量", "开发者评估", "developer score".

Why this skill is useful

Provides domain-specific analysis commands and structured reporting for evaluating developer performance that the AI wouldn't reliably generate on its own.

What it needs

Requires click, gitpython, jinja2, pdfkit, pydriller, radon, reportlab, tabulate, weasyprint installed locally. About 8k tokens when loaded. Last updated 2026-04-26. 34 stars on the source repository.

What this skill does

Code Analysis Skill 📦 GitHub: https://github.com/Wscats/code-analysis-skills Scan specified repositories or directories containing Git repositories, analyze and compare developers' commit habits, work patterns, development efficiency, code style, code quality, and slacking index. Provide blunt, data-driven evaluations for each developer with scores, grades, strengths, weaknesses, and actionable suggestions. Output structured reports in Markdown / HTML / JSON / PDF. 💬 Natural Language (Recommended) You don't need to memorize any commands — simply describe what you need in your own language: 🇺🇸 English 🇨🇳 中文 🇯🇵 日本語 🇰🇷 한국어 🇪🇸 Español 🇫🇷 Français 🇩🇪 Deutsch Note: You need to provide the repository path (repopath) — it is a required parameter. If you are already working within a repository context, the agent may infer the path from the conversation, but an explicit path is always recommended for accuracy. The Skill understands all the languages above. Just describe what you need and it will run the analysis on your repository and return a structured report. --- 🚀 Quick Start (CLI) Install Dependencies For higher quality PDF output (optional): Common Commands CLI Parameters Parameter Short Description Default ----------- ------- ------------- --------- --repo-path -r Path to Git repository or parent directory Required --scan-all Recursively scan all .git repositories false --author -a Filter by author (repeatable) All authors --since -s Start date (ISO format) None --until -u End date (ISO format) None --branch -b Branch to analyze Active branch --format -f Output format: markdown, json, html, pdf (comma-separated for multiple) markdown --output -o Output file path stdout --- Use Cases Analyze developer behavior in a Git repository Compare team members' commit habits and development efficiency Understand code quality trends and style consistency Batch-analyze all .git repositories under a directory Generate work habit reports (active hours, weekend/late-n …

How to use it

Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:

@skills bighardperson/code-analysis-skills

View the source on GitHub

Browse the @skills marketplace