Skills git-analysis

📦

git-analysis

Name: git-analysis
Author: 1natsu172

Content revision r1 Safe ⚙️ External commands📁 Filesystem access

Analyze Git Changes

Reviewing branch changes can be slow when commits, diffs, and status are scattered. This skill gathers Git context for PRs, reviews, and commit planning.

Supports: Claude Codex Code(CC)

🥉 78 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "git-analysis" from https://skillstore.io/skills/1natsu172-git-analysis.md and its manifest at https://skillstore.io/api/skills/1natsu172-git-analysis/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/1natsu172-git-analysis.md Signed manifest GET /api/skills/1natsu172-git-analysis/manifest Signed lockfile GET /api/skills/1natsu172-git-analysis/lockfile

Test it

Using "git-analysis". Analyze the current feature branch before a pull request.

Expected outcome:

Branch summary with base branch, merge base, commit count, changed files, and notable diffs.

Using "git-analysis". Review the commit history since divergence.

Expected outcome:

A concise commit timeline.
Potentially noisy or unclear commits.
Suggested pull request narrative.

Using "git-analysis". Compare staged and unstaged changes before committing.

Expected outcome:

A working tree summary that separates staged changes, unstaged changes, and untracked files.

Security Audit

Safe

v8 • 7/9/2026 Open versioned report

Most static findings are expected git-analysis behavior, safe helper scripts, or Markdown command examples. The confirmed issue is a reference workflow that writes repository status and diffs to predictable /tmp/git_*.txt files. No prompt-injection text or malicious exfiltration intent was found.

Files scanned

776

Lines analyzed

Review items

False positives ignored

Capability review items (11)

These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.

Medium

REFERENCE.md:235

Temp directory access

git status > /tmp/git_status.txt 2>&1 &

The reference workflow uses predictable /tmp/git_*.txt paths for repository status and diff data. If copied, this can expose sensitive local changes or allow local temp-file tampering on shared systems.

Medium

REFERENCE.md:238

Temp directory access

git diff --cached > /tmp/git_diff_staged.txt 2>&1 &

Medium

REFERENCE.md:241

Temp directory access

git diff > /tmp/git_diff_unstaged.txt 2>&1 &

Medium

REFERENCE.md:247

Temp directory access

git log --oneline $MERGE_BASE..HEAD > /tmp/git_commits.txt 2>&1 &

Medium

REFERENCE.md:250

Temp directory access

git diff --stat $MERGE_BASE..HEAD > /tmp/git_stats.txt 2>&1 &

Medium

REFERENCE.md:258

Temp directory access

cat /tmp/git_status.txt

Medium

REFERENCE.md:262

Temp directory access

cat /tmp/git_diff_staged.txt

Medium

REFERENCE.md:266

Temp directory access

cat /tmp/git_diff_unstaged.txt

Medium

REFERENCE.md:270

Temp directory access

cat /tmp/git_commits.txt

Medium

REFERENCE.md:274

Temp directory access

cat /tmp/git_stats.txt

Medium

REFERENCE.md:277

Temp directory access

rm -f /tmp/git_*.txt

Risk Factors

⚙️ External commands (71)

REFERENCE.md:50 REFERENCE.md:169 REFERENCE.md:179 REFERENCE.md:180 REFERENCE.md:181 REFERENCE.md:195 REFERENCE.md:212 REFERENCE.md:213 REFERENCE.md:219 REFERENCE.md:221 REFERENCE.md:222 REFERENCE.md:223 REFERENCE.md:224 REFERENCE.md:244 REFERENCE.md:245 REFERENCE.md:285 REFERENCE.md:286 REFERENCE.md:346 REFERENCE.md:371 REFERENCE.md:372 REFERENCE.md:400 REFERENCE.md:403 REFERENCE.md:414 REFERENCE.md:415 scripts/get_branch_diff.sh:27 scripts/get_branch_diff.sh:30 scripts/get_branch_diff.sh:38 scripts/get_branch_diff.sh:41 scripts/get_branch_diff.sh:45 scripts/get_branch_diff.sh:46 scripts/get_branch_diff.sh:47 scripts/get_commit_history.sh:26 scripts/get_commit_history.sh:27 SKILL.md:31 SKILL.md:33-35 SKILL.md:35-43 SKILL.md:43-46 SKILL.md:46-54 SKILL.md:54-66 SKILL.md:66-72 SKILL.md:72-81 SKILL.md:81-96 SKILL.md:96-98 SKILL.md:98-101 SKILL.md:101-106 SKILL.md:106-113 SKILL.md:113-115 SKILL.md:115-118 SKILL.md:118-120 SKILL.md:120-133 SKILL.md:133-143 SKILL.md:143-147 SKILL.md:147-151 SKILL.md:151-155 SKILL.md:155-160 SKILL.md:160-165 SKILL.md:165-173 SKILL.md:173-190 SKILL.md:190-202 SKILL.md:202-219 SKILL.md:138 SKILL.md:139 SKILL.md:149 SKILL.md:157 SKILL.md:158 SKILL.md:159 SKILL.md:187 SKILL.md:133-143 SKILL.md:147-151 SKILL.md:155-160 SKILL.md:173-190

📁 Filesystem access (26)

Audited by: codex View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/1natsu172-git-analysis/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/1natsu172-git-analysis/security.svg)](https://skillstore.io/skills/1natsu172-git-analysis?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/1natsu172-git-analysis?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/1natsu172-git-analysis/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/1natsu172-git-analysis.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

1natsu172. (2026). git-analysis security audit report (audit version 8) [Author version unspecified]. Skillstore. https://skillstore.io/skills/1natsu172-git-analysis/audits/8

BibTeX citation

@techreport{1natsu172-1natsu172-git-analysis-2026,
  author = {1natsu172},
  title = {git-analysis security audit report (audit version 8)},
  institution = {Skillstore},
  year = {2026},
  number = {8},
  url = {https://skillstore.io/skills/1natsu172-git-analysis/audits/8},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "git-analysis security audit report (audit version 8)"
version: "unspecified"
type: report
authors:
  - name: "1natsu172"
date-released: "2026-07-09"
url: "https://skillstore.io/skills/1natsu172-git-analysis/audits/8"
identifiers:
  - type: other
    value: "skillstore:1natsu172-git-analysis:audit:8"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Prepare a Pull Request

Summarize commits, changed files, and diff statistics before drafting a pull request.

Review Feature Branches

Compare a branch against its merge base to focus review effort.

Audit Release Changes

List commit history and file impact for release notes or team handoff.

Try These Prompts

Summarize My Branch

Use git-analysis to summarize the current branch against the default branch. Include commit count, changed files, and main risks.

Prepare PR Context

Analyze this repository for a pull request. Group changes by area and list commits that need mention.

Review Commit History

Use git-analysis to inspect commits from the merge base to HEAD. Highlight unclear commits and review focus areas.

Classify Branch Changes

Perform a deep branch analysis. Classify changes by file type, connect commits to touched areas, and identify follow-up questions.

Best Practices

Run from the repository root or clearly state the target repository path.
Review generated diffs before sharing because they may contain secrets.
Verify the detected default branch when repositories use nonstandard branch names.

Avoid

Do not run full diff analysis on repositories that contain secrets you cannot expose.
Do not assume origin/main when the repository reports a different default branch.
Do not use predictable temporary files from reference examples on shared systems.