Git History Analyzer
CheckedAnalyze Git repositories to identify commit patterns, contributors, and potential code quality issues.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add ratacat/claude-skills --skill git-history-analyzer -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
ratacat
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned ratacat/claude-skills at d4b471d05d.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- d4b471d05d
- Scanned
- 1 file, 44 lines
About this skill
What it does
This skill analyzes Git repository history. It can identify when specific files were added or modified, and pinpoint the commits responsible for those changes. This allows users to understand project evolution and track down the origin of particular code segments.
When to use it
- Debugging: Quickly find out which commit introduced a bug by searching for file modifications around the time the issue started appearing.
- Code Review: Understand the history behind a specific piece of code before approving a pull request.
- Project Understanding: Get an overview of how a project has evolved over time, including when key features were added.
- Auditing: Determine who made changes to sensitive files and when.
Key capabilities
- File change history tracking
- Commit identification based on file modifications
- Date-based filtering of commits
Example prompts
- "Show me the commit history for
src/main.py." - "When was
README.mdfirst added to this repository?" - "List all commits that modified
config/settings.jsonafter 2023-10-26."
Tips & gotchas
The skill requires access to a Git repository URL. Ensure the provided URL is valid and accessible for accurate analysis.