Git History Analyzer
CheckedAnalyzes Git history to identify code contributors, commit patterns, and potential areas of technical debt.
Install on your platform
git-history-analyzer. udecode/plate has no skill named "git-history-analyzer" any more. It was renamed, moved or deleted upstream.We check each listing against its upstream repository with the rules the skills CLI uses, last on 2026-10-30. We don't show a command we know will fail.
What we know about this skill
Publisher
udecode
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 udecode/plate at 92b1eb95e0.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 92b1eb95e0
- Scanned
- 1 file, 65 lines
About this skill
What it does
The udecode-git-history-analyzer skill analyzes Git repository history. It allows users to understand commit patterns, identify contributors, and gain insights into project evolution over time. This tool is particularly useful for debugging, auditing, or understanding the development process of a codebase.
When to use it
- Debugging complex issues: Investigate when a bug was introduced by examining commit history around that timeframe.
- Code review preparation: Quickly understand the context and changes made in specific commits before reviewing them.
- Understanding project ownership: Identify key contributors and their areas of expertise within a repository.
- Auditing code changes: Review historical modifications to ensure compliance or security standards.
Key capabilities
- Analyzes Git commit history
- Identifies contributors to the codebase
- Provides insights into project evolution
Example prompts
- "Analyze the git history of [repository URL] and tell me who made the most commits."
- "Show me the commit history for [file path] in [repository URL]."
- "What was changed in commit [commit hash]?"
Tips & gotchas
The skill requires a valid Git repository URL as input. The accuracy of the analysis depends on the quality and completeness of the Git history data available.