git-best-practices

Pass

Audited by Gen Agent Trust Hub on Aug 9, 2026

Risk Level: SAFE
Full Analysis
  • [SAFE]: The skill promotes secure development practices by explicitly instructing the agent to exclude sensitive files like .env, secrets, and credentials from commits.
  • [SAFE]: It utilizes standard, well-known development tools such as git and gh (GitHub CLI) for repository operations.
  • [SAFE]: The use of --force-with-lease is recommended for force-pushing, which is a recognized safety mechanism to prevent overwriting remote work unexpectedly.
  • [SAFE]: Instructions focus on formatting (conventional commits) and workflow organization (branch naming and discovery) without introducing external dependencies or remote execution vectors.
Audit Metadata
Risk Level
SAFE
Analyzed
Aug 9, 2026, 05:07 PM
Security Audit — agent-trust-hub — git-best-practices