brikko-studio-secret-scanning-maintainer

What problem does it solve?

GitHub secret scanning alerts flag leaked credentials in public repository content, and maintainers need a standardized, secure workflow to redact exposed secrets, notify affected authors, and resolve alerts without leaving plaintext sensitive data in edit histories or public outputs.

Core Features & Use Cases

• Multi-location alert processing: Handles secret leaks in issue comments, PR comments, discussion comments, issue/PR bodies, and commit content.
• Secure redaction workflow: Automatically deletes and recreates comments to purge edit history, redacts issue/PR bodies in place, and never exposes plaintext secrets in public comments or logs.
• Automated notification and resolution: Sends standardized security notices to affected authors and resolves alerts with the correct resolution status, with full audit trail generation.
• Use case: When a contributor accidentally leaks an API key in a PR comment, this skill automatically redacts the key, notifies the author to rotate the credential, deletes the original comment to purge edit history, and resolves the secret scanning alert.

Quick Start

Use the brikko-studio-secret-scanning-maintainer skill to process all open secret scanning alerts for the Brikko Studio repository, redact exposed credentials, notify affected authors, and resolve the alerts securely.