fleet-updating-hooks-dry

Audit fleet hook trees and oxlint plugin configurations for duplication and bloat.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Fleet updating hooks tend to grow and drift, creating repeated logic and hard-to-maintain configurations. This Skill analyzes the fleet hook tree, the oxlint plugin, and related guard rules to surface copy-paste patterns, dead _shared exports, overlapping enforcers, and long-hook smells, and it outputs a prioritized plan for consolidation without making changes.

Core Features & Use Cases

  • Detects copy-paste clusters across .claude/hooks/fleet and .claude/hooks/repo excluding _shared.
  • Flags dead _shared exports and potential replacements with shared helpers.
  • Ranks consolidation opportunities by impact, with evidence and a concrete sketch for changes.
  • Provides a read-only report suitable for review before refactoring or PR creation.

Quick Start

Run the read-only fleet-hooks dry-sweep to generate a ranked consolidation report under .claude/reports/hooks-dry-sweep-YYYY-MM-DD.md.

Frequently Asked Questions about fleet-updating-hooks-dry

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

FAQPage Schema
How do I identify duplicate logic across fleet hooks before refactoring?

Fleet hook consolidation detects copy-paste clusters across .claude/hooks/fleet and .claude/hooks/repo while excluding _shared exports, generating a read-only ranked report of duplication evidence without applying changes.

What is a read-only dry-sweep for hook consolidation?

A read-only dry-sweep audits the fleet hook tree and oxlint plugin configurations to surface dead _shared exports, overlapping enforcers, and long-hook smells, outputting a prioritized consolidation plan with concrete sketches.

How do I find dead _shared exports in my fleet hook tree?

Finding dead _shared exports involves validating detector scripts and existing gate checks against the .claude/hooks directory to flag unused exports and propose potential replacements with shared helpers.

Can I audit oxlint plugin configurations for overlapping enforcers on demand?

Yes, you can audit oxlint plugin configurations on demand or on a schedule to identify overlapping enforcers and bloat, producing a ranked consolidation report under .claude/reports/ without modifying the repository.

Does the hook consolidation report apply changes directly to the repository?

No, the hook consolidation report is strictly read-only and plan-only, meaning it generates evidence and concrete consolidation sketches for review before any refactoring or PR creation occurs.

What's the best way to rank hook consolidation opportunities by impact?

Ranking hook consolidation opportunities by impact requires analyzing copy-paste patterns and long-hook smells, then validating findings against existing detector scripts to produce a prioritized, evidence-backed consolidation sketch.