Pywayne Bin Gitstats

Analyze and visualize Git commit time distribution. Use when users need to analyze Git repository commit patterns, generate commit statistics, visualize comm...

Security Scan

The skill's described functionality (a gitstats CLI) is plausible, but the package provides no install instructions or code and the metadata fails to declare required binaries/dependencies, leaving an incoherent and unverifiable runtime surface.

Purpose & Capability

The SKILL.md clearly describes a gitstats CLI that requires Git and Python packages (pandas, matplotlib, and a package named 'pywayne'), but the registry metadata lists no required binaries or dependencies and there are no code files. It's unclear where the 'gitstats' executable comes from or how dependencies are provided—this mismatch is disproportionate to the stated purpose.

Instruction Scope

The instructions are narrowly focused on analyzing a repository and producing image output; they direct running a local CLI, reading a repository path, and writing/overwriting output files (including absolute paths). That's consistent with the stated aim, but because the skill has no code/install spec, the runtime instructions are unverifiable. Also note the skill will read repository contents (arbitrary filesystem paths supplied by the user), which is expected for this task but is a data-scope consideration the user should review.

Install Mechanism

There is no install specification and no code files, yet SKILL.md claims requirements ('Git must be installed' and 'Python dependencies: pandas, matplotlib (installed with pywayne)'). The skill provides no source for 'pywayne' or the 'gitstats' binary. An instruction-only skill that expects a specific CLI without telling where it comes from is incoherent and risky—users cannot verify the origin of the executable or dependencies.

Credentials

The skill requests no environment variables, no credentials, and no config paths in metadata. That is proportionate to a local repository analysis tool. However, the SKILL.md does expect system-level tools (git, python packages) that are not declared—this inconsistency is already flagged under other dimensions.

Persistence & Privilege

The skill is not always-enabled and does not request elevated privileges. Autonomous invocation is allowed (platform default). There is no evidence the skill attempts to modify other skills or system-wide settings.

What to consider before installing

This skill describes a command-line tool ('gitstats') but supplies no code, install instructions, or trusted source for the binary/dependencies. Before installing or invoking it: 1) Ask the publisher for a clear install spec or the source repository (PyPI/GitHub) so you can inspect the code and confirm provenance. 2) Verify that 'gitstats' (or 'pywayne') is a legitimate package from a trusted source; do not run an unknown binary from an untrusted origin. 3) Be aware the tool will read repository files you point it at and will write/overwrite image files at chosen paths—avoid pointing it at sensitive directories. 4) If you must run it, do so in a sandboxed environment (container/VM) and check network activity and the package's installation steps first. If the publisher cannot provide a verifiable source or install instructions, treat the skill as untrusted.

Analyze Git repository commit time distribution and generate visualizations.

Quick Start

# Analyze current repository (default: current directory, current branch)
gitstats

# Specify custom output path
gitstats --save output.png

# Analyze with time filter
gitstats --since "2024-01-01"

Usage Examples

Basic Analysis

# Analyze current repository
gitstats

# Analyze specific repository path
gitstats /path/to/repo

# Show plot in popup window (no file saved)
gitstats -p

Time Range Filtering

# Commits since specific date
gitstats --since "2024-01-01"

# Commits within date range
gitstats --since "2024-01-01" --until "2024-12-31"

# Relative time expressions
gitstats --since "1 year ago"
gitstats --since "90 days ago"
gitstats --until "30 days ago"

Branch Selection

# Analyze specific branch
gitstats --branch main
gitstats --branch develop
gitstats --branch origin/main

# Analyze all branches
gitstats --all

Timezone Configuration

# Use UTC timezone
gitstats --tz UTC

# Use specific timezone
gitstats --tz "America/New_York"
gitstats --tz "Europe/London"

# Default is Asia/Shanghai
gitstats --tz "Asia/Shanghai"

Custom Output

# Custom output filename
gitstats --save my_stats.png

# Output to subdirectory
gitstats --save results/commit_analysis.png

# Absolute path
gitstats --save /tmp/git_stats.png

Combined Examples

# All branches, last year, custom output
gitstats --since "1 year ago" --all --save yearly_stats.png

# Main branch, last 90 days, UTC timezone
gitstats --branch main --since "90 days ago" --tz UTC

# Develop branch, date range, show plot
gitstats --branch develop --since "2024-01-01" --until "2024-06-30" -p

Command Reference

Argument	Description
repo	Git repository path. Default: current directory
--since	Start time (e.g., "2024-01-01", "1 year ago", "90 days ago")
--until	End time (same formats as --since)
--tz	Timezone. Default: "Asia/Shanghai". Examples: "UTC", "America/New_York"
--branch	Specific branch to analyze. Examples: "main", "develop", "origin/main"
--all	Analyze all branches (overrides --branch)
--save	Output image path. Default: "git_time_distribution.png"
-p, --show-plot	Show plot in popup window without saving file

Output Charts

Generates a 3×2 subplot layout visualization:

1. Commits per Day - Line chart showing daily commit counts
2. Commits by Hour - Bar chart for hours 0-23
3. Commits by Weekday - Bar chart for Mon-Sun
4. Heatmap: Weekday × Hour - Color-coded activity matrix

Chart title includes: repository name, branch, and timezone.

Branch Selection Priority

1. If --all is specified, all branches are analyzed
2. If --branch is specified, only that branch is analyzed
3. If neither is specified, current HEAD branch is used

Requirements

• Git must be installed
• Python dependencies: pandas, matplotlib (installed with pywayne)

Notes

• Time range can use Git's flexible date formats (absolute dates, relative expressions)
• Output file is overwritten if it exists
• Large repositories with --all may take longer to process
• Commit times are parsed in UTC, then converted to specified timezone