github-cleanup

Audit GitHub repositories for failing workflows, stale forks, and orphaned secrets.

3|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/spm1001/claude-suite --skill github-cleanup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-cleanup
Source: https://github.com/spm1001/claude-suite/tree/main/skills/github-cleanup
Command: npx skills add https://github.com/spm1001/claude-suite --skill github-cleanup

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

GitHub hygiene is error-prone when auditing workflows, forks, secrets, and security settings. This skill standardizes the process by auditing across repos, surfacing issues in a consolidated report, and ensuring only approved actions are executed.

Core Features & Use Cases

  • Audit-funnel: scan all repos for failing workflows, stale forks, orphaned secrets, and security configurations.
  • Consolidated findings: present clear, actionable findings for user review.
  • Guarded execution: execute changes only after explicit user approval and post-check verification.

Quick Start

Start with a full account audit to surface all issues, then review findings and approve targeted actions before proceeding.

Frequently Asked Questions about github-cleanup

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

FAQPage Schema
How do I audit all my GitHub repositories for failing workflows and orphaned secrets?

To audit GitHub repositories for failing workflows and orphaned secrets, run a full account scan across all repos. This consolidates security configurations, stale forks, and workflow failures into a single actionable report for targeted cleanup.

What is the safest way to clean up stale forks and security configurations across a GitHub account?

The safest way to clean up stale forks and security configurations is an audit, present, approve, and execute workflow. This enforces explicit user approval for destructive actions and performs cross-checks to prevent accidental data loss.

Do I need the gh CLI installed to scan my GitHub repos for orphaned secrets?

Yes, you need the gh CLI installed and authenticated to scan GitHub repos for orphaned secrets. The audit relies on the gh CLI to access all repositories within your authenticated user account safely.

Can I automatically delete stale forks and failing workflows without manual approval?

No, you cannot automatically delete stale forks or failing workflows without manual approval. The execution phase enforces explicit user approval for destructive steps and performs post-check verification to prevent accidental data loss.

Why does my GitHub cleanup workflow require an audit before executing destructive actions?

Your GitHub cleanup requires an audit before destructive actions to surface all issues in a consolidated report. This cross-checking phase prevents accidental data loss by ensuring you review and approve targeted actions before execution.