skills.rest
ahandsel
ahandselCOMMUNITY
Explore all skills by this author →
GitHub

file-folder-name-linter

Validate repository file and folder names against kebab-case and extension standards.

1|Updated May 21, 2020
Search Tags:#automation#git#linting#code-quality#repository-management#naming-convention
One-click install
npx skills add https://github.com/ahandsel/debugging_log --skill file-folder-name-linter
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: file-folder-name-linter
Source: https://github.com/ahandsel/debugging_log/tree/main/skills/file-folder-name-linter
Command: npx skills add https://github.com/ahandsel/debugging_log --skill file-folder-name-linter

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill solves the issue of inconsistent file and folder naming conventions within a repository, which often leads to navigation difficulties and broken documentation links.

Core Features & Use Cases

  • Naming Convention Enforcement: Automatically validates that files and folders follow kebab-case, correct date-prefixed note formats, and proper file extensions.
  • Automated Remediation: Safely renames .yml files to .yaml to ensure consistency across the project.
  • Use Case: Use this skill during a repository audit to identify non-compliant file structures and ensure all new notes follow the required YYYY-MM-DD-kebab-name.md format.

Quick Start

Run the linter across the entire repository to identify and report any naming convention violations.

Frequently Asked Questions about file-folder-name-linter

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

FAQPage Schema
How do I enforce kebab-case naming conventions for files and folders in a git repository?▼

You can enforce kebab-case naming conventions by running a linter that validates git-tracked paths against predefined rules. This identifies non-compliant file and folder names automatically, ensuring repository structure consistency.

What is the best way to automate renaming .yml files to .yaml across a project?▼

Automated remediation tools can safely rename .yml files to .yaml to ensure extension consistency. This automated renaming functionality corrects file extensions across the project without manual intervention.

How do I validate date-prefixed note formats like YYYY-MM-DD in a codebase?▼

Validating date-prefixed note formats requires a linter that checks file names against required YYYY-MM-DD-kebab-name.md patterns. This ensures all new notes follow the correct date and formatting structure.

Do I need a git-initialized environment to check repository naming standards?▼

Yes, a git-initialized environment is required to check repository naming standards. The linter operates on git-tracked paths to enumerate files and apply project-specific naming rules accurately.

Can I audit an entire repository for broken documentation links caused by inconsistent file names?▼

Auditing a repository for inconsistent file names helps prevent broken documentation links. Running a linter across the entire repository identifies non-compliant file structures that typically cause navigation difficulties.

Related Skills

Explore More Software Engineering Skills→
haackedhaacked
127

note

Create, find, list, and update structured notes in git-tracked repositories.

Community
Basic
knckknckknckknck

wcag-audit-patterns

Audit WCAG 2.2 conformance with axe-core, pa11y, and lighthouse.

Community
Advanced
hector-mannyhector-manny

coding-standards

Enforce naming, readability, immutability, and code-quality review principles.

Community
Advanced
cjdutoitcjdutoit
3

the-standard-code-csharp

Validate C# source code for style rules, naming conventions, and comment formatting.

Community
Basic