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 |
lint check <input> |
Record a syntax/code check entry |
lint validate <input> |
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 |
lint stats |
Show summary statistics — entry counts per category, total entries, data size, and earliest activity timestamp |
lint export <fmt> |
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:
~/.local/share/lint/
├── check.log # Check entries
├── validate.log # Validation entries
├── generate.log # Generation entries
├── format.log # Formatting entries
├── lint.log # Lint pass entries
├── explain.log # Explanation entries
├── convert.log # Conversion entries
├── template.log # Template entries
├── diff.log # Diff entries
├── preview.log # Preview entries
├── fix.log # Fix entries
├── report.log # Report entries
├── history.log # Unified activity log
└── export.* # Export output files
Requirements
- Bash (with
set -euo pipefail)
- Standard Unix utilities:
date, wc, du, head, tail, grep, basename, cut
- No external dependencies or API keys required
When to Use
- 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
# Record a check on a Python file
lint check "src/main.py — 3 unused imports found"
# Record a fix applied
lint fix "Removed unused imports in src/main.py"
# View recent formatting actions
lint format
# Search for all entries mentioning "import"
lint search import
# Export everything to JSON
lint export json
# View overall statistics
lint stats
# Health check
lint status
Powered by BytesAgain | bytesagain.com | hello@bytesagain.com
1---2name: lint3description: Check code syntax, enforce style, and suggest auto-fixes with CI integration. Use when linting PRs, enforcing code style, detecting errors before merge.4license: MIT-05---6
7# Lint
8
9Lint 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.
10
11## Commands
12
13### Core Action Commands
14
15Each 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.
16
17| Command | Description |
18|---------|-------------|
19| `lint check <input>` | Record a syntax/code check entry |
20| `lint validate <input>` | Record a validation result |
21| `lint generate <input>` | Record a code generation action |
22| `lint format <input>` | Record a formatting operation |
23| `lint lint <input>` | Record a linting pass |
24| `lint explain <input>` | Record an explanation or annotation |
25| `lint convert <input>` | Record a conversion operation |
26| `lint template <input>` | Record a template action |
27| `lint diff <input>` | Record a diff comparison |
28| `lint preview <input>` | Record a preview action |
29| `lint fix <input>` | Record an auto-fix action |
30| `lint report <input>` | Record a report generation |
31
32### Utility Commands
33
34| Command | Description |
35|---------|-------------|
36| `lint stats` | Show summary statistics — entry counts per category, total entries, data size, and earliest activity timestamp |
37| `lint export <fmt>` | Export all data to JSON, CSV, or TXT format. Output file saved to `~/.local/share/lint/export.<fmt>` |
38| `lint search <term>` | Full-text search across all log files (case-insensitive) |
39| `lint recent` | Show the 20 most recent entries from the history log |
40| `lint status` | Health check — version, data directory, total entries, disk usage, last activity |
41| `lint help` | Show help with all available commands |
42| `lint version` | Print version string (`lint v2.0.0`) |
43
44## Data Storage
45
46All 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.
47
48**Directory structure:**
49```
50~/.local/share/lint/
51├── check.log # Check entries
52├── validate.log # Validation entries
53├── generate.log # Generation entries
54├── format.log # Formatting entries
55├── lint.log # Lint pass entries
56├── explain.log # Explanation entries
57├── convert.log # Conversion entries
58├── template.log # Template entries
59├── diff.log # Diff entries
60├── preview.log # Preview entries
61├── fix.log # Fix entries
62├── report.log # Report entries
63├── history.log # Unified activity log
64└── export.* # Export output files
65```
66
67## Requirements
68
69- Bash (with `set -euo pipefail`)
70- Standard Unix utilities: `date`, `wc`, `du`, `head`, `tail`, `grep`, `basename`, `cut`
71- No external dependencies or API keys required
72
73## When to Use
74
751. **Tracking linting sessions** — Record which files you linted, what issues you found, and what fixes you applied, all with timestamps for audit trails.
762. **Code review workflows** — Log check and validate results during PR reviews so you can refer back to what was inspected and when.
773. **Template and diff management** — Keep a running record of template operations and diff comparisons across project iterations.
784. **Exporting quality reports** — Use `lint export json` to generate machine-readable reports of all recorded lint activity for CI dashboards or team reviews.
795. **Searching past actions** — Quickly find previous lint results, fixes, or explanations with `lint search <term>` across all categories.
80
81## Examples
82
83```bash
84# Record a check on a Python file
85lint check "src/main.py — 3 unused imports found"
86
87# Record a fix applied
88lint fix "Removed unused imports in src/main.py"
89
90# View recent formatting actions
91lint format
92
93# Search for all entries mentioning "import"
94lint search import
95
96# Export everything to JSON
97lint export json
98
99# View overall statistics
100lint stats
101
102# Health check
103lint status
104```
105
106---
107
108Powered by BytesAgain | bytesagain.com | hello@bytesagain.com
bytesagain