Code Viewer

A comprehensive devtools toolkit for checking, validating, formatting, linting, explaining, converting, diffing, previewing, and fixing code — with built-in logging, search, statistics, and data export.

Commands

Usage

code-viewer <command> [args]

Each command with an argument logs the input with a timestamp and saves it to a category-specific log file. Running a command without arguments displays the most recent entries for that category.

Data Storage

• Default location: ~/.local/share/code-viewer
• Log files: Each command category stores entries in its own file (e.g., check.log, lint.log, diff.log)
• History: All commands are also logged to history.log with timestamps
• Export formats: JSON (structured array), CSV (type/time/value), or plain text

Requirements

• Bash 4+ (strict mode: set -euo pipefail)
• No external dependencies or API keys required
• Standard Unix tools (date, wc, grep, du, head, tail)

When to Use

1. Code review workflow — Use check, lint, and validate to log and track code issues during review sessions
2. Learning and documentation — Use explain to break down unfamiliar code, then report to generate summaries
3. Format conversion — Use convert to transform code between formats, and format to standardize style
4. Diff tracking — Use diff to log code comparisons, then search to find specific changes later
5. Team metrics and audit — Use stats to see activity summaries, export json to feed data into dashboards

Examples

# Check a code snippet
code-viewer check "function add(a, b) { return a + b; }"

# Lint a file reference
code-viewer lint "src/main.js has unused imports"

# Explain a code block
code-viewer explain "Array.prototype.reduce callback"

# View diff history
code-viewer diff

# Generate a report entry
code-viewer report "Sprint 12 code quality summary"

# Show aggregate stats across all categories
code-viewer stats

# Export all data as JSON
code-viewer export json

# Search logs for a keyword
code-viewer search "reduce"

# Show recent activity
code-viewer recent

# Health check
code-viewer status

Output

• Command results print to stdout
• All entries are timestamped and persisted to ~/.local/share/code-viewer/<category>.log
• Export files are written to ~/.local/share/code-viewer/export.<fmt>

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