openclaw-secret-scanning-maintainer

Triage, redact, and resolve OpenClaw secret-scanning alerts across issues, PRs, and discussions.

7|12|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/borealBytes/my-farm-advisor --skill openclaw-secret-scanning-maintainer-borealbytes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openclaw-secret-scanning-maintainer
Source: https://github.com/borealBytes/my-farm-advisor/tree/main/.agents/skills/openclaw-secret-scanning-maintainer
Command: npx skills add https://github.com/borealBytes/my-farm-advisor --skill openclaw-secret-scanning-maintainer-borealbytes

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Triage, redact, clean up, and resolve OpenClaw GitHub Secret Scanning alerts in issues or PRs.

Core Features & Use Cases

  • Maintains secret scanning hygiene by patching bodies, deleting and recreating comments, and posting targeted notifications.
  • Handles multiple alert locations including discussion comments via GraphQL and issue/PR bodies via REST, with auditing and summary.

Quick Start

Run the secret-scanning.mjs tool to fetch an alert, inspect its locations with fetch-alert, then process each location through fetch-content, redact, purge, and notify.

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 automate redacting GitHub secret scanning alerts in issues and PRs?

Automate GitHub secret scanning alert redaction by patching issue and PR bodies via REST, deleting and recreating comments, and posting targeted notifications to maintainers without manual intervention.

Can I purge secret scanning alerts from GitHub discussion comments using GraphQL?

Yes, secret scanning alerts in GitHub discussion comments can be purged using GraphQL orchestration to fetch content, redact secrets, and edit the comment bodies to remove exposed credentials.

What is the best way to triage OpenClaw secret scanning alerts across multiple repository locations?

Triage OpenClaw secret scanning alerts by fetching the alert, inspecting all locations, then systematically processing each through content retrieval, redaction, history purging, and standardized notification.

Does this secret scanning triage workflow require special GitHub permissions to edit or delete comments?

Maintainer permissions are required to edit or delete comments, redact bodies, and purge history where possible, ensuring secure handling of exposed secrets across issues, PRs, and discussions.

How are redacted secret scanning alerts summarized for repository maintainers?

Redacted secret scanning alerts are summarized through maintainable auditing outputs that track patched bodies, deleted comments, and posted notifications across all processed alert locations.

Why should I use an automated tool for secret scanning alert resolution instead of manually editing comments?

Automated secret scanning resolution ensures secure handling by hiding secrets and using random temp files, orchestrating GraphQL and REST efficiently, and standardizing notifications without human error.