Filesystem

oimiragieo/agent-studio/.claude/skills/filesystem

by oimiragieo64b580eab27ba37673f042ecc12ac53413cd9dd5No licenseListed Oct 9, 2026Updated Oct 9, 2026

File system operations guidance - read, write, search, and manage files using Claude Code's built-in tools.

Includes scriptsSoftware Development
AI-generated overview

Guides agents in reading, writing, searching, and managing files with built-in file tools.

What it does
This skill provides guidance for file system operations using an agent's built-in tools. It covers reading single or multiple files, creating and modifying files, finding files by glob pattern, searching file contents, and basic directory operations. It also documents recommended workflows such as read-before-edit, parallel reads, and search-then-edit, plus a memory protocol for recording learnings, issues, and decisions.
When to use it
Use it when an agent needs to read, create, edit, locate, or search files during a task. It is also relevant when establishing consistent file-handling practices, such as reading before editing or preferring structured search tools over raw shell commands.
Requirements
Requires an agent environment with built-in file tools (Read, Write, Edit, Bash, Glob, Grep). Content search guidance references pnpm search:code or a ripgrep skill. Ships executable scripts (scripts/main.cjs, hooks/pre-execute.cjs, hooks/post-execute.cjs) and schema, rule, template, and reference files.

Filesystem Skill

<identity>

Filesystem Skill - Guidance for file system operations using Claude Code's built-in tools. Read, write, search, and manage files efficiently.

</identity>

<capabilities>

  • Reading single or multiple files
  • Creating or modifying files
  • Searching for files by pattern
  • Searching file contents
  • Directory navigation

</capabilities>

<instructions>

<execution_process>

Claude Code Built-in Tools

Reading Files

Read Tool: Read file contents

Read file_path="/path/to/file.txt"

Options:

  • offset: Start line (for large files)
  • limit: Number of lines to read

Finding Files

Glob Tool: Find files by pattern

Glob pattern="**/*.ts"

Common patterns:

  • **/*.ts - All TypeScript files
  • src/**/*.tsx - React components in src
  • **/test*.js - Test files anywhere

Searching Content

Primary Search: Use pnpm search:code "query" or Skill({ skill: 'ripgrep' }) for content searching. The built-in Grep tool is fallback-only.

Grep Tool: Search file contents (fallback only — prefer pnpm search:code or ripgrep skill first)

Grep pattern="function myFunc" path="/src"

Options:

  • output_mode: "content", "files_with_matches", or "count"
  • -A, -B, -C: Context lines

Writing Files

Write Tool: Create or overwrite files

Write file_path="/path/to/file.txt" content="..."

Edit Tool: Modify existing files

Edit file_path="/path/to/file.txt" old_string="..." new_string="..."

Directory Operations

Bash Tool: For directory operations

bash
# List directoryls -la /path/to/dir
# Create directorymkdir -p /path/to/new/dir
# Move/renamemv /old/path /new/path

</execution_process>

<best_practices>

Common Workflows

Reading Multiple Files

# Read files in parallel (multiple Read calls in one message)Read file_path="/src/app.ts"Read file_path="/src/config.ts"Read file_path="/src/utils.ts"

Search and Read

# 1. Find filesGlob pattern="**/*.config.ts"
# 2. Read matching filesRead file_path="/path/from/glob/result"

Find and Replace

# 1. Search for patternGrep pattern="oldFunction" path="/src"
# 2. Edit each fileEdit file_path="/src/file.ts" old_string="oldFunction" new_string="newFunction"

Best Practices

  1. Read Before Edit: Always read a file before editing it
  2. Use Glob Over Bash: Prefer Glob to find for file discovery
  3. Search Tool Hierarchy: Use pnpm search:code or Skill({ skill: 'ripgrep' }) first; use the Grep tool as fallback over raw bash grep only
  4. Parallel Reads: Read multiple files in one message for speed
  5. Verify Changes: Read file after editing to verify

</best_practices>

</instructions>

<examples>

<usage_example>

Find and read all TypeScript files:

Glob pattern="src/**/*.ts"# Then read the resultsRead file_path="/src/app.ts"

</usage_example>

<usage_example>

Search for a function and edit it:

Grep pattern="export function oldName" path="/src"# Found in /src/utils.ts:23
Edit file_path="/src/utils.ts" old_string="export function oldName" new_string="export function newName"

</usage_example>

</examples>

Rules

  • Always read files before editing
  • Use built-in tools (Read, Glob, Grep) instead of bash equivalents
  • Verify changes after editing

Memory Protocol (MANDATORY)

Before starting:

bash
cat .claude/context/memory/learnings.md

After completing:

  • New pattern -> .claude/context/memory/learnings.md
  • Issue found -> .claude/context/memory/issues.md
  • Decision made -> .claude/context/memory/decisions.md

ASSUME INTERRUPTION: Your context may reset. If it's not in memory, it didn't happen.

Source and attribution

Source:oimiragieo/agent-studioin.claude/skills/filesystemat commit64b580e

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal