How does it handle multiple matching rules for a single file?

It identifies all matching rules and displays them in a prioritized list, with more specific path patterns taking precedence over generic ones.

Does it support recursive directory matching?

Yes, the skill supports the ** pattern for recursive matching across multiple directory levels, ensuring deep file structures are covered.

Can I use this to find files not covered by any rules?

Yes. It effectively identifies files that do not match any existing rule patterns, helping you maintain 100% documentation coverage.

How do I test if a new path pattern will work?

You can provide the proposed glob pattern and a sample file path to the skill, and it will perform a test match to confirm if they align.

Does this require any special configuration files?

It works automatically with the standard .claude/rules/ directory used by Claude Code for managing project-specific instructions.

File Path Matcher

Name: File Path Matcher
Author: biwakonbu

bybiwakonbu

Productivity & Workflow

Validates and visualizes which project-specific rules apply to specific file paths to ensure consistent code standards.

About

The File Path Matcher skill streamlines repository management by determining exactly which rules in .claude/rules/ cover specific files. By parsing glob patterns and frontmatter metadata, it provides instant clarity on rule coverage, helps debug complex path patterns, and ensures developers or AI agents follow the correct architectural guidelines before modifying code. This tool is essential for maintaining governance in large projects where manual verification of rule applicability is difficult and error-prone.

Key Features

Support for recursive matching using standard shell expansion patterns
Rule prioritization logic based on pattern specificity and naming
Automated glob pattern matching for complex directory structures
0 GitHub stars
Comprehensive coverage reports for individual files or entire directories
Frontmatter extraction and parsing from .claude/rules/ markdown files

Use Cases

Identifying 'dead zones' in projects where no coding standards or rules are currently applied
Testing new glob patterns in rule files to prevent unintended rule overlaps
Verifying rule applicability before refactoring or editing sensitive files

About

Key Features

Support for recursive matching using standard shell expansion patterns
Rule prioritization logic based on pattern specificity and naming
Automated glob pattern matching for complex directory structures
0 GitHub stars
Comprehensive coverage reports for individual files or entire directories
Frontmatter extraction and parsing from .claude/rules/ markdown files

Use Cases

Identifying 'dead zones' in projects where no coding standards or rules are currently applied
Testing new glob patterns in rule files to prevent unintended rule overlaps
Verifying rule applicability before refactoring or editing sensitive files