regenerate-merged-rule-lists

mmm1h's avatarfrom mmm1h

Regenerate aggregated *Merged.list files from their source headers in this repo. Use when refreshing upstream sources or rebuilding merged rule lists.

⭐2stars🔀0forks📁View on GitHub🕐Updated Jan 11, 2026⬇️2downloads

When & Why to Use This Skill

This Claude skill automates the maintenance and regeneration of aggregated rule lists (Merged.list) from multiple source headers. It streamlines the workflow of fetching upstream data, merging entries into a consistent Clash classical format, and automatically updating critical metadata such as timestamps and rule counts to ensure configuration integrity.

Use Cases

  • Upstream Source Refreshing: Automatically synchronize and update local rule sets whenever upstream providers modify their source headers or content.
  • Rule Consolidation: Efficiently merge multiple disparate network filter lists into a single, optimized file while maintaining the required execution order.
  • Automated Metadata Management: Keep rule list headers, versioning, and entry counts accurate without manual intervention, reducing the risk of configuration errors in network tools.
  • Format Standardization: Convert various incoming rule formats into a unified 'Clash classical' format to ensure compatibility across different network environments.
nameregenerate-merged-rule-lists
descriptionRegenerate aggregated *Merged.list files from their source headers in this repo. Use when refreshing upstream sources or rebuilding merged rule lists.

Regenerate Merged Rule Lists

Overview

Regenerate *Merged.list files from the sources listed in their headers and keep the metadata intact.

Workflow

  • Open the target *Merged.list and read the header to identify source URLs and expected format.
  • Fetch each source and merge the rules into a single list, preserving the expected order.
  • Keep the header format consistent; update timestamps, counts, and source lines to match the new output.
  • Ensure all rule lines use Clash classical format and keep one rule per line.

Guardrails

  • Avoid manual edits to merged lists unless you are regenerating from sources.
  • Do not remove or rewrite the source header format; keep it consistent across updates.

Quick checks

  • Verify the first lines are the header with sources and update time.
  • Spot-check a few entries to confirm correct formatting and no obvious truncation.