skills.rest
AmirulAndalib
AmirulAndalibCOMMUNITY
Explore all skills by this author →
GitHub

openclaw-secret-scanning-maintainer

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

Updated Jun 19, 2026
Search Tags:#security#github#incident response#gh cli#redaction#secret scanning#credential leak
One-click install
npx skills add https://github.com/AmirulAndalib/Vilvona-AI --skill openclaw-secret-scanning-maintainer-amirulandalib
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openclaw-secret-scanning-maintainer
Source: https://github.com/AmirulAndalib/Vilvona-AI/tree/main/.agents/skills/openclaw-secret-scanning-maintainer
Command: npx skills add https://github.com/AmirulAndalib/Vilvona-AI --skill openclaw-secret-scanning-maintainer-amirulandalib

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Leaked credentials posted in GitHub issues, PRs, comments, and discussions expose the project to compromise, and cleaning them up safely requires careful redaction, edit-history purging, author notification, and alert resolution without ever re-exposing the secret. ## 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. - Location-Aware Remediation: Redact issue/PR bodies in place, delete and recreate leaked comments (including discussion comments via GraphQL), and notify authors with the correct template per location type. - Safe Resolution and Reporting: Resolve alerts with maintainer-only resolution comments and produce a verbatim summary table of actions taken and remaining edit-history risks. - Use Case: A maintainer receives a GitHub Secret Scanning alert for a Discord bot token posted in an issue comment; the skill fetches the content, deletes and recreates the comment in redacted form, 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 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 as a maintainer?▼

Fetch the alert and its locations with the gh CLI, redact or remove the leaked content, notify the author to rotate the credential, then PATCH the alert to state resolved with a resolution such as revoked. The script automates each of these steps.

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

Delete the comment entirely and recreate it with redacted content rather than editing it, because editing leaves the plaintext secret in the edit history. Deletion removes all edit history revisions via the GitHub API.

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 this cannot be cleared via the API. Maintainers must contact GitHub Support to request a purge of userContentEdits.

Does the script expose plaintext secrets in terminal output?▼

No, all alert fetches use hide_secret=true, body content is written to temp files with owner-only permissions, and the script never prints .secret or .body values to stdout. Only the agent reads the body file to produce redactions.

What permissions are needed to handle secret scanning alerts?▼

Repository admin or maintainer permissions are required, since the workflow edits or deletes other users' comments, patches issue and PR bodies, and resolves secret scanning alerts through the GitHub API.

Related Skills

Explore More Software Engineering Skills→
LawrenceHwangLawrenceHwang

secret-scanning

Detect and remediate leaked credentials across GitHub repositories.

Community
Advanced
Nandansai08Nandansai08
1

secrets-incident-response

Rotates leaked credentials, audits usage across the exposure window, and purges git history.

Community
Intermediate
arbazkhan971arbazkhan971
26

secrets

Detect exposed secrets and rotate credentials into secret managers.

Community
Advanced
lens-studio-devslens-studio-devs
16

specs-snap-cloud

Connect Specs Lenses to Snap Cloud backends for databases, realtime sync, storage, and edge functions.

Official
Advanced