enclawed-secret-scanning-maintainer

Remediate GitHub secret scanning alerts by fetching alert metadata and associated locations without exposing plaintext secrets. The Skill triages exposures, removes content, and resolves the alert safely without printing sensitive values.

Remove exposed secrets from GitHub comments by deleting and recreating the comment. This workflow eliminates the secret from the current content and removes the edit history that previously stored the exposed plaintext.

Yes, this secret scanning remediation workflow supports GitHub discussions and replies. It uses GraphQL-based delete and recreate flows to remove exposed credentials from discussion comments and their nested replies.

Yes, you can process multiple GitHub secret scanning alerts. The workflow supports multi-alert processing, updates alert resolutions, and generates a final summary to track the remediation incident for compliance purposes.

The best way to notify an author is by posting an English warning comment. This alert triage workflow automatically posts a comment telling the author which secret types were exposed and to rotate them immediately.

Redact exposed secrets in GitHub issue and pull request bodies by performing in-place body redaction. The Skill modifies the existing content directly to remove the leaked credentials while preserving the surrounding text.