Analyze Git repositories for hotspots, author attribution, and secret exposure.
npx skills add https://github.com/haomingz/kimi-skills --skill git-repo-audit
Please help me install this Agent Skill. Skill: git-repo-audit Source: https://github.com/haomingz/kimi-skills/tree/main/skills/git-repo-audit Command: npx skills add https://github.com/haomingz/kimi-skills --skill git-repo-audit
Git history can hide frequently changing files, attribution gaps, and leaked credentials. This skill surfaces hotspots, clarifies who touched what, and scans historical commits for sensitive data exposures.
Analyze a repository to generate hotspots, ownership insights, and secret-risk findings in one run.
High-intent search queries and answers about installing and using this skill.
To scan Git history for secret exposure, you can analyze historical commits to detect potential sensitive data leaks. This process surfaces leaked credentials to inform immediate security remediation and password rotation.
Finding hotspot files in a Git repository involves analyzing git history and diff stats to identify code with the most changes. This highlights high-churn areas to guide focused code reviews and targeted risk assessment.
Mapping code ownership using Git commits requires analyzing commit metadata to attribute changes to specific contributors. This clarifies who touched what and surfaces last-active dates for better team coordination.
Yes, you can perform a Git repository security audit on codebases of various sizes. The analysis works across different repository scales to uncover hotspots, attribution gaps, and historical secret exposures in one run.
opendatahub-ioCreates a depth-1 clone of a Git repository in a temporary location.
addxaiDetects secret leaks, PII exposure, and compliance violations in code, configuration, and documentation.
LuisSambranoPerform systematic code review and static analysis across multiple programming languages.
alangebAnalyze git diff statistics and scan for debug artifacts.
