Dev Utilities

A developer utility toolkit for tracking, logging, and managing development workflow entries. Records timestamped entries across multiple categories and provides search, export, and reporting capabilities.

Commands

All commands accept optional <input> arguments. Without arguments, they display recent entries from the corresponding log. With arguments, they record a new timestamped entry.

Core Tracking Commands

Utility Commands

Data Storage

• Data directory: ~/.local/share/dev-utilities/
• Log format: Each command writes to its own .log file (e.g., run.log, check.log)
• Entry format: YYYY-MM-DD HH:MM|<input> (pipe-delimited timestamp + value)
• History log: All actions are also appended to history.log with timestamps
• Export output: Written to export.json, export.csv, or export.txt in the data directory

Requirements

• Bash 4+ with set -euo pipefail
• Standard Unix utilities: date, wc, du, grep, tail, cat, sed, basename
• No external dependencies or package installations required

When to Use

• To track and log developer workflow activities with timestamps
• For recording check results, conversions, analyses, or batch operations
• When you need to search across historical development activity logs
• To export tracked data to JSON, CSV, or plain text for external analysis
• For monitoring data directory health and entry statistics

Examples

# Record a new run entry
dev-utilities run "build frontend v3.2"

# Check recent analysis entries
dev-utilities analyze

# Search all logs for a keyword
dev-utilities search "frontend"

# Export all data as JSON
dev-utilities export json

# View summary statistics
dev-utilities stats

# Show recent activity
dev-utilities recent

# Health check
dev-utilities status

Configuration

Set the DEV_UTILITIES_DIR environment variable to override the default data directory. Default: ~/.local/share/dev-utilities/

Output

All commands write results to stdout. Redirect output with dev-utilities <command> > output.txt.

Powered by BytesAgain | bytesagain.com | hello@bytesagain.com