categorizing-files

Name: categorizing-files
Availability: InStock
Author: hernamesbarbara

Classify project files into eight standard categories with a CLI script.

Updated Nov 25, 2025

Search Tags:#codebase #cli #taxonomy #mapping #categorize #files

Ready to run

npx skills add https://github.com/hernamesbarbara/promptkit --skill categorizing-files

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: categorizing-files
Source: https://github.com/hernamesbarbara/promptkit/tree/main/.claude/skills/categorizing-files
Command: npx skills add https://github.com/hernamesbarbara/promptkit --skill categorizing-files

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill defines the standard eight-category taxonomy for classifying project files: Config, Tests, Docs, Scripts, Source Code, Data, AI Tooling, and Other. It provides clear rules to map files and directories to these categories, reducing ambiguity and speeding up audits.

Core Features & Use Cases

Taxonomy: Fixed eight categories with explicit scope.
Mapping Rules: Directory and filename patterns map files to categories consistently.
Tooling: A bundled CLI script to categorize entire projects and report findings.

Quick Start

Run the categorize.py script on a project root to produce categorized outputs.

Frequently Asked Questions about categorizing-files

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

FAQPage Schema

How do I categorize files in my project into standard taxonomy?▼

File categorization maps your codebase into eight standard categories: Config, Tests, Docs, Scripts, Source Code, Data, AI Tooling, and Other. Run the bundled categorize.py script on your project root to classify files by directory patterns, filenames, and content structure, producing a standardized report of how files map to each category.

What are the eight file categories in this taxonomy?▼

The taxonomy defines Config (configuration files), Tests (test suites), Docs (documentation), Scripts (automation and tooling), Source Code (application code), Data (datasets and resources), AI Tooling (machine learning and AI artifacts), and Other (unclassified files). Each category has explicit scope and mapping rules applied consistently across your repository.

Can I run file categorization on an existing codebase without modifying it?▼

Yes. The categorization process scans your repository tree and produces categorized output without changing your files. The CLI script respects directory exclusions and priority rules, allowing you to audit and report on project structure while preserving your original code.

How does the categorization handle edge cases and mixed file types?▼

Categorization applies a four-phase classification approach: Phase 1 matches directory and filename patterns, Phase 2 checks frontmatter signals, Phase 3 analyzes content structure, and Phase 4 detects keywords. Layered exclusion handling and per-file priority rules resolve ambiguous cases consistently.

What output does the categorization script produce?▼

The script generates a standardized per-file output schema mapping each file in your codebase to one of the eight categories. Results are formatted for repository audits and automated analysis, showing which files belong to Config, Tests, Docs, Scripts, Source Code, Data, AI Tooling, or Other.