skills.rest
JEROME-PRAKASH-L
JEROME-PRAKASH-LCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

openclaw-secret-scanning-maintainer

Triage, redact, and resolve GitHub secret scanning alerts in issues and pull requests.

1|Updated Jun 9, 2026
Search Tags:#security#github#incident response#gh cli#redaction#secret scanning#credential leak
One-click install
npx skills add https://github.com/JEROME-PRAKASH-L/openclaw --skill openclaw-secret-scanning-maintainer-jerome-prakash-l
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openclaw-secret-scanning-maintainer
Source: https://github.com/JEROME-PRAKASH-L/openclaw/tree/main/.agents/skills/openclaw-secret-scanning-maintainer
Command: npx skills add https://github.com/JEROME-PRAKASH-L/openclaw --skill openclaw-secret-scanning-maintainer-jerome-prakash-l

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Leaked credentials in GitHub issues, PRs, comments, and discussions expose the project to compromise, and cleaning them up requires careful redaction, edit-history purging, author notification, and alert resolution across many location types. ## Core Features & Use Cases - Alert Triage and Content Fetching: List open secret scanning alerts and fetch affected content with hide_secret=true so plaintext secrets never appear in terminal output. - Redaction and History Purging: Redact issue/PR bodies in place, or delete and recreate leaked comments (including discussion comments via GraphQL) to wipe edit history. - Notification and Resolution: Post templated English security notices to authors, skip notifications when the body is already redacted, resolve alerts, and produce a formatted summary table. - Use Case: A maintainer receives a GitHub Secret Scanning alert for a Discord bot token posted in an issue comment; the skill fetches the comment, deletes it, recreates a redacted version, notifies the author to rotate the credential, and resolves the alert. ## Quick Start Ask the agent to list all open secret scanning alerts for the openclaw repository and process alert number 72 end to end.

Frequently Asked Questions about openclaw-secret-scanning-maintainer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I resolve GitHub secret scanning alerts in issues and PRs?▼

Fetch the alert metadata and affected content, redact any remaining plaintext secrets, purge comment edit history by deleting and recreating the comment, notify the author to rotate credentials, then resolve the alert with a resolution such as revoked.

How to remove a leaked secret from a GitHub comment history?▼

Delete the comment entirely and recreate it with redacted content, since editing only adds a new revision and keeps the plaintext in edit history. For discussion comments, use the GraphQL deleteDiscussionComment and addDiscussionComment mutations.

Can you purge edit history from a GitHub issue or PR body?▼

No, editing an issue or PR body always creates a userContentEdits revision containing the pre-edit plaintext, and the API cannot clear it. Maintainers must contact GitHub Support to request a purge of userContentEdits for that issue or PR.

What permissions are needed to manage secret scanning alerts?▼

Repo admin or maintainer permissions are required to edit or delete other users' comments and to resolve secret scanning alerts. The workflow runs through the GitHub CLI (gh), which must be authenticated with an appropriately scoped token.

Why should redacted secrets not include partial values or prefixes?▼

Including any portion of a secret, even a prefix or suffix, reduces the search space for attackers and confirms part of the credential. The skill replaces each secret entirely with a marker like [REDACTED <secret_type>] and never prints secrets to stdout.

Related Skills

Explore More Software Engineering Skills→
githubgithub
38.5k

secret-scanning

Configure GitHub secret scanning, push protection, custom patterns, and alert remediation workflows.

Official
Intermediate
DuqueOMDuqueOM
5

secret-breach-response

Detect leaked credentials in repositories, logs, or artifacts and initiate incident response.

Community
Advanced
latestaiagentslatestaiagents
5

secrets-detection

Detect leaked API keys and credentials in code repositories.

Official
Intermediate
brikkoAIbrikkoAI
1

brikko-studio-secret-scanning-maintainer

Automate triage, redaction, and resolution of GitHub secret scanning alerts.

Official
Advanced