Lint
Lint is a developer-focused toolkit for recording and tracking code quality operations from the terminal. It provides 13 core action commands for managing checks, validations, formatting, linting, code generation, conversions, templates, diffs, previews, fixes, reports, and explanations — all with timestamped local logging for full traceability. Additional utility commands let you view statistics, export data, search history, and monitor health status.
Commands
Core Action Commands
Each action command works in two modes: run without arguments to view the 20 most recent entries, or pass input text to record a new timestamped entry.
| Command | Description |
|---|
| INLINECODE0 | Record a syntax/code check entry |
| INLINECODE1 |
Record a validation result |
|
lint generate <input> | Record a code generation action |
|
lint format <input> | Record a formatting operation |
|
lint lint <input> | Record a linting pass |
|
lint explain <input> | Record an explanation or annotation |
|
lint convert <input> | Record a conversion operation |
|
lint template <input> | Record a template action |
|
lint diff <input> | Record a diff comparison |
|
lint preview <input> | Record a preview action |
|
lint fix <input> | Record an auto-fix action |
|
lint report <input> | Record a report generation |
Utility Commands
| Command | Description |
|---|
| INLINECODE12 | Show summary statistics — entry counts per category, total entries, data size, and earliest activity timestamp |
| INLINECODE13 |
Export all data to JSON, CSV, or TXT format. Output file saved to
~/.local/share/lint/export.<fmt> |
|
lint search <term> | Full-text search across all log files (case-insensitive) |
|
lint recent | Show the 20 most recent entries from the history log |
|
lint status | Health check — version, data directory, total entries, disk usage, last activity |
|
lint help | Show help with all available commands |
|
lint version | Print version string (
lint v2.0.0) |
Data Storage
All data is stored locally in ~/.local/share/lint/. Each action command writes to its own log file (e.g., check.log, validate.log, fix.log). A unified history.log records every action with timestamps. No external services, databases, or network connections are used.
Directory structure:
CODEBLOCK0
Requirements
- - Bash (with
set -euo pipefail) - Standard Unix utilities:
date, wc, du, head, tail, grep, basename, INLINECODE34 - No external dependencies or API keys required
When to Use
- 1. Tracking linting sessions — Record which files you linted, what issues you found, and what fixes you applied, all with timestamps for audit trails.
- Code review workflows — Log check and validate results during PR reviews so you can refer back to what was inspected and when.
- Template and diff management — Keep a running record of template operations and diff comparisons across project iterations.
- Exporting quality reports — Use
lint export json to generate machine-readable reports of all recorded lint activity for CI dashboards or team reviews. - Searching past actions — Quickly find previous lint results, fixes, or explanations with
lint search <term> across all categories.
Examples
CODEBLOCK1
Powered by BytesAgain | bytesagain.com | hello@bytesagain.com
