Git Cli 1.0.0

PassAudited by ClawScan on May 1, 2026.

Overview

This instruction-only Git helper is coherent and benign, but its normal Git commands can change or publish repository contents if the user runs them.

This skill appears safe as a Git command reference. Before using write or sync commands, check `git status`, review diffs, confirm the branch and remote, and be careful that `git add .` can include unintended files such as secrets.

Findings (2)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

What this means

Running these commands could commit unintended files or push code to a shared remote repository.

Why it was flagged

The skill documents Git commands that can stage many files and publish commits to a remote repository. This is expected for the stated purpose, but users should review changes before running these commands.

Skill content
Stage all tracked and untracked changes: `git add .` ... For subsequent pushes on the same branch: `git push`
Recommendation

Use `git status` and `git diff` first, verify the branch and remote, and avoid `git add .` or `git push` unless the intended changes are clear.

What this means

The skill may not work unless Git is already installed, but there is no evidence of hidden installation or execution behavior.

Why it was flagged

The skill depends on a local Git binary, while the registry requirements list no required binaries. Because there is no install script or bundled code, this is only a dependency declaration gap.

Skill content
- Git is installed and available on the PATH (for example `git --version` succeeds).
Recommendation

Confirm Git is installed from a trusted source before using the command examples.