Skip to content
Back to skills

Core File Ops

ASecurity

Perform batch file operations safely with search, replacement, renaming, or refactoring.

  • 2 stars
  • 0 votes
  • 0 copies
  • 4 views
  • Added September 8, 2026
code-qualitybashrefactoringgit

Security analysis

A100/100

Scanned September 8, 2026

npx -y skills add nobodyonlyc/skills --skill core-file-ops --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Core File Ops?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Core File Ops
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/nobodyonlyc-core-file-ops/badge)](https://www.skillsdirectory.com/skills/nobodyonlyc-core-file-ops)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: core-file-ops
description: Perform batch file operations safely with search, replacement, renaming, or refactoring.
---

File operation task: $ARGUMENTS

Gather context about the files involved:

```bash
# Understand scope
echo "=== Current directory ==="
ls -la
echo "=== Git status ==="
git status --short
```

Identify what kind of operation is needed and execute it:

**Search & inspect**
- Find files by name, extension, or content pattern
- Show file sizes, counts, structure

**Transform & rewrite**
- Batch rename, move, or reorganize files
- Convert formats (JSON↔YAML, CSV↔TSV, etc.)
- Find-and-replace across multiple files

**Generate & scaffold**
- Create files from a template or pattern
- Scaffold directory structures

**Analyze**
- Diff two files or directories
- Detect duplicates, orphans, or broken references
- Summarize large files (line count, structure, top entries)

Rules:
1. **Preview before destructive actions** — show what will change and get confirmation before deleting, moving, or overwriting files.
2. **Prefer targeted edits** — use Edit tool for small changes; only rewrite whole files when necessary.
3. **Preserve git history** — use `git mv` instead of raw `mv` when renaming tracked files.
4. After completion, show a summary: files affected, before/after if relevant.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…