Omni Tool

All-in-one terminal utility toolkit for running, checking, converting, analyzing, generating, and managing tasks from the command line. Omni Tool provides 12 core action commands plus built-in statistics, data export, search, and health-check capabilities — all backed by local log-based storage.

Commands

All commands follow the pattern: INLINECODE0

When called without arguments, each command displays its most recent 20 log entries.
When called with arguments, it records the input with a timestamp.

Core Action Commands

Utility Commands

Data Storage

All data is stored locally in plain-text log files:

• - Location: INLINECODE24
• Format: Each entry is a line of YYYY-MM-DD HH:MM|<input> in the corresponding <command>.log file
• History: Every action is also appended to history.log with a timestamp and command label
• Export formats: JSON (array of objects), CSV (with headers), plain text (grouped by command)
• No external dependencies — pure bash, runs anywhere

Requirements

• - Bash 4.0+ (uses set -euo pipefail)
• Core utilities: date, wc, du, tail, grep, sed, cat, INLINECODE36
• No network access required — fully offline
• No configuration needed — works out of the box

When to Use

1. 1. Quick task logging — capture run results, check outcomes, or conversion records from the terminal without opening a separate app
2. Batch processing workflows — use omni-tool batch to log batch job details, then omni-tool stats to review totals
3. Data analysis pipelines — record analysis steps with omni-tool analyze, then omni-tool export json for downstream processing
4. Configuration auditing — track config changes with omni-tool config and search history with INLINECODE42
5. Cross-entry reporting — combine omni-tool report with omni-tool stats and omni-tool export csv to produce summary reports across all command categories

Examples

Record a run and view recent entries

CODEBLOCK0

Analyze, then export results

CODEBLOCK1

Search and report

CODEBLOCK2

Batch processing workflow

CODEBLOCK3

Health check and comparison

CODEBLOCK4

Output

All commands output to stdout. Redirect to a file with:

CODEBLOCK5