Git命令行助手专业版

• Outcome: Review
• Latest audit: Aug 29, 2026 · 5:13 AM UTC
• Version: 1.0.1

Overview

This Git automation skill is mostly aligned with its purpose, but it needs review because it can automatically stage, commit, push, rebase, and delete branches across repositories without clear user-controlled safeguards.

Install only if you want an agent to perform Git-changing operations. Before use, require explicit confirmation for commits, pushes, rebases, tags, branch deletion, and multi-repo cleanup; avoid git add -A defaults; review diffs and target repositories first; and do not use the persistent Git credential store unless that matches your security policy.

SkillSpector

Vulnerability Patterns

• Data Exfiltration: External Transmission, Env Variable Harvesting, File System Enumeration
• Excessive Agency: Unrestricted Tool Access, Autonomous Decision Making, Scope Creep
• Trigger Abuse: Overly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
• Behavioral AST: exec() Call, eval() Call, Dynamic Import
• MCP Tool Poisoning: Hidden Instructions, Unicode Deception, Parameter Description Injection

Findings (11)

Context-Inappropriate Capability

Medium

• Confidence: 84% confidence
• Finding: The skill states no extra API key is needed, yet its interface includes a callback_url and later documentation discusses networked behavior. This mismatch can cause operators to treat the skill as local-only while it may transmit data externally, increasing the risk of unintended data exfiltration or unsafe deployment in restricted environments.

Intent-Code Divergence

Medium

• Confidence: 80% confidence
• Finding: The documentation claims no extra API key is required, but the security guidance later assumes secret handling via environment variables and remote authentication setup. This inconsistency can mislead users about secret usage and trust boundaries, causing insecure setup or accidental exposure of credentials in automation contexts.

Intent-Code Divergence

Medium

• Confidence: 91% confidence
• Finding: The skill asserts that dangerous operations require confirmation, but elsewhere promotes unattended automation such as auto-push, auto-cleanup, and batch cleanup. In a Git automation context, this can lead to irreversible branch deletion, unwanted commits, or propagation of bad state across multiple repositories without an interactive safety check.

Vague Triggers

Medium

• Confidence: 78% confidence
• Finding: The trigger condition is broad enough to activate the skill for vague requests about efficiency, automation, batch processing, or workflow optimization. In a skill with exec/write capabilities, overbroad invocation increases the chance that the agent applies potentially state-changing Git automation when the user did not intend repository modification.

Missing User Warnings

Medium

• Confidence: 90% confidence
• Finding: The examples show automated commit/sync/cleanup behavior with exec-enabled shell and Python snippets, but without prominent warnings about side effects or prerequisites. In repository management, such examples normalize write operations that can modify history, push unintended content, or disrupt team workflows, especially if copied directly into production environments.

Missing User Warnings

Medium

• Confidence: 88% confidence
• Finding: The batch cleanup example presents multi-repository cleanup without clear explanation of what will be removed or whether recovery is possible. In a multi-repo context, a mistaken cleanup action can scale a single operator error into widespread branch or workspace loss across many repositories.

Missing User Warnings

Medium

• Confidence: 96% confidence
• Finding: The smart_commit example automatically stages all modified and untracked files with `git add -A` and immediately commits them, without any confirmation, path allowlist, or preview. In an enterprise Git automation skill, this can easily cause accidental inclusion of secrets, generated files, or unrelated changes into version control.

Missing User Warnings

Medium

• Confidence: 95% confidence
• Finding: The sync workflow performs `fetch`, conditional `pull --rebase`, and `push` automatically against remotes without an explicit warning or operator confirmation. In a multi-user repository, this can rewrite local history, trigger unintended remote updates, or propagate bad commits with a single invocation.

Missing User Warnings

High

• Confidence: 98% confidence
• Finding: The feature-branch completion flow deletes both the local branch and the remote branch immediately after merge, with no confirmation or rollback guidance. Branch deletion is destructive and can remove recovery points or disrupt collaborators still using the branch.

Missing User Warnings

High

• Confidence: 98% confidence
• Finding: The Bash workflow examples perform merge, push, local branch deletion, and remote branch deletion as a bundled flow without clear warnings. Because these are copy-pastable shell functions, users may execute destructive operations in production repositories without understanding the side effects.

Missing User Warnings

High

• Confidence: 99% confidence
• Finding: The batch_cleanup example enumerates merged branches and deletes them across multiple repositories automatically, which amplifies the blast radius of mistakes. In enterprise multi-repo contexts, one misconfigured repo list or incorrect merge assumption can cause widespread branch loss and operational disruption.

VirusTotal

VirusTotal findings are pending for this skill version.

Static analysis

No suspicious patterns detected.