git-workflows
Pass
Audited by Gen Agent Trust Hub on Sep 1, 2026
Risk Level: SAFECOMMAND_EXECUTIONEXTERNAL_DOWNLOADSDYNAMIC_EXECUTIONINDIRECT_PROMPT_INJECTIONPRIVILEGE_ESCALATIONREMOTE_CODE_EXECUTION
Full Analysis
- [COMMAND_EXECUTION]: The skill facilitates local Git management through a wide range of commands, including those for history modification such as
rebase,reset, andfilter-repo. Safety is maintained by instructions requiring recovery refs and explicit authorization for state-changing operations.\n- [DYNAMIC_EXECUTION]: The skill provides instructions to configure the local Git environment to run a hook script from its assets (assets/commit-msg). It also includes templates for setup and audit scripts which are executed locally.\n- [EXTERNAL_DOWNLOADS]: Reference documentation includes examples of fetching repository patches and diffs from GitHub usingcurl. These operations target a well-known, trusted service.\n- [REMOTE_CODE_EXECUTION]: The documentation describes piping external patches directly into Git commands (curl ... | git am). While this executes remote content, the source is a trusted service (GitHub).\n- [INDIRECT_PROMPT_INJECTION]: The skill ingests untrusted data from Git logs, diffs, and external patches, creating an attack surface for indirect prompt injection.\n - Ingestion points: Git history, diff outputs, repository status, and downloaded patch files.\n
- Boundary markers: The 'commit-slicing contract' and validation steps like
git diff --checkserve as delimiters and check points.\n - Capability inventory: Git command execution, hook configuration, and local file writes.\n
- Sanitization: The
commit-msghook uses regex to validate inputs.\n- [PRIVILEGE_ESCALATION]: The skill instructs the user to applychmod +xto grant necessary execution permissions to hook scripts.
Audit Metadata