Local file assistant

Problem: I have scattered files across project folders. Finding, organizing, and batch-editing without writing shell scripts every time.

Setup: Hermes + Ollama offline, started from project root.

Use case 1: Find and report

Scan ~/Projects/FDE/hermes-course/hermes-mastery-docs/docs recursively.
List every .md file with its path and word count.
Sort by word count descending. Show top 10.

What Hermes does: run_command (find/wc) or read_file across directories, aggregates results.

Result: A table I use to spot thin pages that need more content.

Use case 2: Batch rename / organize

In docs/use-cases/, all files should follow kebab-case naming.
Check current filenames, list any that don't match, and propose
renames. Wait for my approval before renaming.

What Hermes does: Lists directory, checks naming, proposes changes, waits for approval, renames.

Lesson learned: Always say "wait for approval." Without it, Hermes renamed files I didn't want touched.

Use case 3: Generate missing README sections

Read README.md in the project root. Compare it to the actual
docs/ folder structure. Update README to reflect all current
sections. Keep the same tone and length.

What Hermes does: Reads README + scans docs/, edits README in place.

Use case 4: Dead link check (offline)

Run npm run build in the project root. If the build fails due to
dead links, list each broken link with source file and target.
Do not fix them yet.

What Hermes does: Runs build, parses VitePress error output, reports links.

Tips for file work

• Start sessions from the project directory (loads context files).
• Be explicit about approval before destructive ops.
• Local Qwen 3.5 (27B) handles file tasks well; speed is the main constraint.
• After doing this 3+ times, Hermes created a skill for "audit docs project."

Benchmark

If this use case takes under 60 seconds on your hardware, your offline setup is healthy.