resolving-merge-conflicts

Pass

Audited by Gen Agent Trust Hub on Sep 11, 2026

Risk Level: SAFEINDIRECT_PROMPT_INJECTIONNO_CODE
Full Analysis
  • [INDIRECT_PROMPT_INJECTION]: The skill requires the agent to read and resolve git conflict hunks, which are untrusted external inputs that could contain malicious instructions.\n
  • Ingestion points: File content during merge/rebase conflict resolution (SKILL.md, Steps 1-3).\n
  • Boundary markers: None. There are no explicit markers used to separate untrusted code from instructions.\n
  • Capability inventory: Execution of project tests, typecheckers, and git commands (SKILL.md, Steps 4-5).\n
  • Sanitization: None. The skill focuses on resolving intent rather than validating the safety of the code being merged.\n- [NO_CODE]: The skill does not contain any scripts, binaries, or configuration files, relying solely on markdown instructions.
Audit Metadata
Risk Level
SAFE
Analyzed
Sep 11, 2026, 02:04 AM
Security Audit — agent-trust-hub — resolving-merge-conflicts