openclaw-secret-scanning-maintainer

To redact secrets in GitHub issues and PRs, this Skill fetches the exposed content, prepares redacted bodies, and deletes or recreates comments via GraphQL to remove sensitive data. It then notifies the author and closes the alert.

Yes, you can automatically resolve secret scanning alerts for discussions by fetching alert metadata, redacting the leaked secrets, and using GraphQL operations to update the discussion content and close the alert with proper notification.

The best way to notify maintainers after redacting exposed credentials is to use clear notification templates that explain the redaction, post them to the relevant issue or PR, and generate JSON output for auditing and handoff.

This secret scanning workflow uses both REST and GraphQL APIs to fetch alert locations and delete or recreate GitHub comments, ensuring sensitive content is fully removed while preserving the discussion context.

You audit redacted secret scanning alerts by executing the script-driven workflow that processes alerts end-to-end and outputs JSON files summarizing the redacted secrets, notified authors, and resolved alerts for handoff.