file-operations_skill

Overview

This skill analyzes files and returns detailed metadata and content statistics without modifying files. It extracts size, modification times, line counts, and pattern-based content metrics. Use it to get quick, non-destructive insights about individual files or entire directories.

How this skill works

The skill inspects file system metadata (size, modification timestamp) and computes line counts with lightweight scanning. For content analysis it reads files and runs pattern searches to count functions, imports, TODOs, or other regex matches. It favors efficient operations (stat, wc, grep-style scans, and globbing) and avoids any write operations.

When to use it

• Request file info or a summary for one or more files
• Count lines, functions, classes, imports, or TODOs in source files
• Compare file sizes or modification times across a project
• Find large files or unusual files that impact build or deploy time
• Audit codebase metrics without changing code or repository state

Best practices

• Always run non-destructive commands (stat, wc, read, grep) to avoid accidental changes
• Read small files fully for deeper analysis; use pattern searches for large files
• Limit scope with glob patterns or directory filters to improve performance
• Compare metrics against project averages to identify outliers
• Exclude common vendor directories (node_modules, .venv) when searching for largest files

Example use cases

• Get size and last-modified time for a specific source file before a code review
• Count total lines and number of test files to estimate test coverage effort
• Find all TODO/FIXME occurrences to prioritize technical-debt work
• Locate the top 20 largest files to reduce repository bloat or speed up CI
• Compare two file versions by line counts and key-pattern frequencies (functions/imports)