thorough-hermes-skill-publishing

To prevent private data leakage when publishing skill artifacts, you can enforce publish-readiness audits and data-leak scanning. This approach scans for secrets, local paths, and identifiers, classifying artifacts as publish-ready or blocked before any repository mutation occurs.

Approval gating for git push and public releases is a safety mechanism requiring explicit approval before copying, syncing, or performing repository mutations. It ensures evidence collection and portability reviews are completed before any public write is authorized.

To run release validation before exporting private skills, execute read-only audits that produce a publish-readiness verdict and remediation steps. This validates packages, archives, and releases while ensuring artifacts are portable or marked private-only.

Yes, secrets scanning can catch .git directory leakage in skill packages. The private-data and portability checks scan for secrets, local paths, identifiers, and .git/ leakage to prevent machine-specific assumptions from entering public artifacts.

Automated publishing safety checks for git hygiene require explicit approval before any repository mutation, meaning they cannot auto-commit changes. They also rely on accurate classification of artifacts as publish-ready or blocked, needing manual review for edge cases.