Use Cases — evolver-tools: Real-World Workflows

01

📊 CSV Data Analysis Pipeline

Got a CSV file from a client or export? Analyze, filter, convert, and visualize it — without opening Excel or writing Python scripts.

csv-stats csv-filter csv-sort csv2json chart-cli csv-pretty

Step 1 — Explore the data

$ csv-stats sales_2025.csv

Columns: date, product, region, units, revenue, margin
Total rows: 12,483 · Missing: margin (87 nulls)
→ revenue: mean ¥2,340, median ¥1,890, max ¥48,200
Generating histogram...

Step 2 — Filter and sort

$ csv-filter sales_2025.csv --column region --value APAC | csv-sort --column revenue --desc | csv-pretty

┌────────────┬──────────┬────────┬─────────┐
│ date │ product │ units │ revenue │
├────────────┼──────────┼────────┼─────────┤
│ 2025-11-15 │ Enterprise│ 342 │ 48,200 │
│ 2025-09-03 │ Pro │ 189 │ 22,680 │
│ ... │ │ │ │
└────────────┴──────────┴────────┴─────────┘
APAC top product: Enterprise (¥48,200)

Step 3 — Chart and export

$ csv2json sales_2025.csv --pretty | json-path '.[*].revenue' | chart-cli --type bar --label "Revenue by row"

Revenue by row
████████████ 48,200 ← peak in Nov
██████░░░░░░ 22,680
████░░░░░░░░ 15,100
██░░░░░░░░░░ 8,400
Tip: pipe csv-slice to chart specific columns

02

🖥️ Server Health Check

Quickly assess server health — CPU, memory, disk, running services, and recent log activity. No need to install htop, ncdu, or tail separately.

sysmon disk-usage log-hawk portcheck process-kill net-analyzer

Step 1 — Overview at a glance

$ sysmon

CPU █████░░░ 62% │ Mem ████████ 82% │ Disk ████░░░ 44%
⚠ Memory at 82% — check for leaks
Top process: node /app/server.js (18% CPU, 1.2GB RSS)

Step 2 — Deep dive

$ disk-usage /var/log --depth 2

/var/log 4.2 GB
├── nginx/ 2.1 GB ← largest
├── journal/ 1.3 GB
└── app/ 0.8 GB
$ portcheck --range 3000-3100
3000 ✓ (Express) · 3001 ✓ (Redis) · 3002 ✗

Step 3 — Logs and action

$ log-hawk /var/log/nginx/error.log --tail 20 --filter "error"

[2026-06-01 14:32:01] ERROR upstream timeout /api/reports
[2026-06-01 14:28:15] ERROR SSL handshake failed from 45.33.32.156
3 occurrences in last 10 minutes — investigate upstream

03

🔌 API Debugging Toolkit

Troubleshoot an API endpoint end-to-end: inspect headers, test endpoints, format responses, and query JSON results — no Postman required.

api-tester http-headers json-pretty json-path http-status siege-lite

Step 1 — Check headers

$ http-headers https://api.example.com/users

HTTP/2 200 OK
server: nginx/1.24
content-type: application/json; charset=utf-8
x-request-id: req_a1b2c3d4
x-rate-limit-remaining: 42
cache-control: no-cache
→ 200 OK, rate limit OK (42 remaining)

Step 2 — Test and format

$ api-tester GET https://api.example.com/users?limit=5 | json-pretty

{
  "users": [
    { "id": 1, "name": "Alice", "role": "admin", "active": true },
    { "id": 2, "name": "Bob", "role": "editor", "active": true },
    ...
  ],
  "pagination": { "page": 1, "total": 342 }
}

Step 3 — Query and load test

$ api-tester GET https://api.example.com/users?limit=5 | json-path '$.users[*].name'

Alice
Bob
Charlie
Diana
Evan
$ siege-lite https://api.example.com/health --concurrent 10 --requests 100
Requests: 100/100 · p50: 45ms · p95: 120ms · p99: 230ms · Errors: 0

04

📋 Code Project Audit

Before a release or handoff, run a full project health check: code stats, structure, changelog, code smells, and license validation.

project-doctor code-stats tree changelog-gen smellfinder license-cli

Step 1 — Health check

$ project-doctor /path/to/project

✅ README.md present
✅ LICENSE (MIT)
⚠️ No CHANGELOG.md — run changelog-gen to generate
✅ .gitignore present
⚠️ CI config not detected

Step 2 — Structure and stats

$ tree /path/to/project --max-depth 2 --dirs-only

project/
├── src/
│ ├── api/
│ ├── core/
│ └── utils/
├── tests/
└── docs/
$ code-stats /path/to/project/src
Python: 12,340 lines · JavaScript: 3,200 lines · Tests: 4,100 lines

Step 3 — Quality and changelog

$ smellfinder /path/to/project/src

⚠️ long-function: process_data.py:142 (48 lines, limit 30)
⚠️ too-many-params: api/handlers.py:89 (7 params, limit 5)
⚠️ bare-except: utils/helpers.py:23
3 issues found — low severity
$ changelog-gen --from v1.0.0 --to HEAD
→ 24 commits · 8 features · 12 fixes · 4 chores

05

🔒 Security Checkup

Scan for leaked secrets, verify file integrity, check SSL certs, and generate strong passwords — all from the terminal.

secret-scanner hashsum cert-check passgen file-encrypt config-vault

Step 1 — Secret scanning

$ secret-scanner /path/to/project --include .env,.py,.json

Scanning 142 files...
⚠ HIGH: .env:14 — AWS Secret Key detected (AKIA*...)
⚠ MED: config.json:23 — potential JWT token
⚠ LOW: test.py:56 — dummy API key in test
→ 1 high-severity issue found!

Step 2 — Integrity verification

$ hashsum /path/to/backup.tar.gz --sha256

a3f2b8c1... backup.tar.gz
$ cert-check example.com
example.com:443 — Valid until 2026-08-15 (75 days remaining) ✓
Issuer: Let's Encrypt · SANs: *.example.com, example.com

Step 3 — Generate and encrypt

$ passgen --length 32 --special --entropy

Password: K9#mP2$xL7@vR5!nQ8*wB4&zF3^tG6
Entropy: 192 bits · Estimated crack time: centuries
$ file-encrypt config.prod.json --out config.enc
✓ Encrypted with AES-256-GCM · Key: config.key (keep safe!)

Real-World Use Cases

📊 CSV Data Analysis Pipeline

🖥️ Server Health Check

🔌 API Debugging Toolkit

📋 Code Project Audit

🔒 Security Checkup

Ready to try it yourself?