file-operations

Analyze files to extract metadata and content statistics without modification.

657|94|Updated Oct 17, 2025
One-click install
npx skills add https://github.com/mhattingpete/claude-skills-marketplace --skill file-operations
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: file-operations
Source: https://github.com/mhattingpete/claude-skills-marketplace/tree/main/code-operations-plugin/skills/file-operations
Command: npx skills add https://github.com/mhattingpete/claude-skills-marketplace --skill file-operations

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually gathering file statistics, line counts, or content details can be time-consuming and error-prone. This Skill automates file analysis, providing quick insights into your codebase without modifying any files.

Core Features & Use Cases

  • Detailed Metadata: Get file size, line counts, and modification times for single or multiple files.
  • Content Analysis: Analyze code structure, count functions, classes, or imports within files.
  • Pattern Search: Quickly find TODOs, FIXMEs, or specific code patterns across your project.
  • Use Case: Ask for a comprehensive analysis of app.py to get its size, line count, and a breakdown of functions and classes, all in seconds.

Quick Start

Get file size and modification time

bash stat -f "%z bytes, modified %Sm" app.py

Count lines in a file

bash wc -l app.py

Read file content for analysis

Read(file_path="app.py")

Frequently Asked Questions about file-operations

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

FAQPage Schema
How do I quickly get file statistics like size and line count without manual inspection?

File analysis extracts metadata such as file size, line counts, and modification times automatically using standard tools. This Skill analyzes single or multiple files instantly, returning structured data without modifying any files, eliminating manual digging through your codebase.

Can I analyze code structure to count functions, classes, and imports across my project?

Content analysis breaks down code structure by parsing files to count functions, classes, imports, and other patterns. You get detailed metrics for single files or entire directories, enabling quick insights into codebase organization and complexity.

How do I search for TODOs, FIXMEs, and specific patterns across multiple files?

Pattern search uses grep and standard Unix tools to find TODOs, FIXMEs, or custom code patterns across your project files. Results are returned in structured format, making it simple to identify technical debt and track pending work without manual file review.

What's the best way to compare file statistics across an entire codebase?

File analysis generates comparable metrics—size, line counts, modification times, and content statistics—for entire directories and codebases. Structured output enables pattern-based queries and integration with auditing or documentation tools for codebase-wide insights.

Does file analysis work non-destructively without modifying my source code?

File analysis is read-only and non-destructive; it extracts metadata and content statistics using stat, ls, du, wc, and grep without altering any files. This makes it safe for continuous inspection, auditing, and integration into automated workflows.