openclaw-secret-scanning-maintainer

To redact secrets leaked in GitHub issues and pull requests, this Skill identifies secrets in content and replaces them with redaction markers. It then purges and recreates affected comments to completely remove leaked content.

The best way to triage GitHub Secret Scanning alerts across discussions is by fetching alert metadata and locations without exposing plaintext secrets, applying redaction workflows, and posting standardized maintenance notifications to stakeholders.

A maintainer safely resolves secret scanning alerts by using a dedicated script that enforces safety constraints, avoiding plaintext output of secrets and requiring explicit maintainer controls for destructive operations like purging or replacing content.

Yes, you can purge and recreate leaked comments on GitHub to remove exposed tokens. The Skill deletes and recreates affected comments and discussion comments to eliminate leaked content from the platform's history.

Destructive secret leak cleanup operations on GitHub require explicit maintainer controls. The Skill enforces safety constraints that mandate maintainer authorization before executing content purging, replacing, or alert resolution actions.