cleaning-ci

Delete orphan workflow YAMLs and disable automated-security-fixes via API.

125|42|Updated May 19, 2025
One-click install
npx skills add https://github.com/SocketDev/socket-mcp --skill cleaning-ci
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cleaning-ci
Source: https://github.com/SocketDev/socket-mcp/tree/main/.claude/skills/fleet/cleaning-ci
Command: npx skills add https://github.com/SocketDev/socket-mcp --skill cleaning-ci

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Audit and clean redundant CI surface across a Socket fleet: orphan workflow files, automated-security-fixes configurations, and stale workflow records that clutter the UI and confuse deployment pipelines.

Core Features & Use Cases

  • Orphan workflow YAML cleanup: Detects and removes per-repo files named lint.yml, check.yml, type.yml, and test.yml that were superseded by the shared ci.yml.
  • GitHub-Dependabot automated-security-fixes toggle: Disables automated-security-fixes for affected repos via API while keeping dependabot.yml untouched.
  • Stale workflow run history cleanup: Deletes sidebar-only workflow records to reflect the current, consolidated CI state.
  • Use Case: Onboard a fleet repository and perform a quarterly cleanup to maintain a clean, predictable CI surface across all fleet projects.

Quick Start

Run the fleet cleaning-ci operation on a repository to inventory CI leftovers and apply a safe cleanup plan.

Frequently Asked Questions about cleaning-ci

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

FAQPage Schema
How do I clean up orphan GitHub Actions workflow files across multiple repositories?▼

To clean up orphan GitHub Actions workflows, the tool inventories fleet repositories to detect redundant YAML files like lint.yml and test.yml, then generates a safe, phased deletion plan with per-repo confirmation before removing them via API.

Can I disable GitHub automated security fixes without modifying dependabot.yml?▼

Yes, you can disable GitHub automated security fixes without modifying dependabot.yml by using the API to toggle the automated-security-fixes setting off for affected repositories while keeping the dependabot.yml configuration file completely untouched.

What is the best way to remove stale workflow run history from a GitHub repository fleet?▼

The best way to remove stale workflow run history is to delete sidebar-only workflow records via API, clearing outdated CI run logs to reflect the current consolidated state without affecting active deployment pipelines.

Does the CI cleanup process enforce read-only inventory before deleting workflow YAMLs?▼

Yes, the CI cleanup process enforces a strict read-only inventory first to surface all remnants safely, followed by per-repo confirmation and API-based deletions with guardrails to prevent unsafe changes across the fleet.

When should I run a CI surface cleanup for my repository fleet?▼

You should run a CI surface cleanup during fleet onboarding to remove legacy files and periodically as a quarterly health check to maintain a clean, predictable CI surface across all projects.

What specific workflow YAML files are targeted for deletion during fleet CI cleanup?▼

The fleet CI cleanup specifically targets per-repo workflow YAML files named lint.yml, check.yml, type.yml, and test.yml for deletion when it detects they have been superseded by a shared, consolidated ci.yml workflow.