Lint 是一款开发者工具，用于记录和跟踪终端下的代码质量操作。它提供 13 个核心操作命令用于管理检查、验证、格式化、linting、代码生成、转换、模板、差异、预览、修复、报告和解释——所有操作都有时间戳的本地日志用于完整的追踪。额外的实用命令允许您查看统计数据、导出数据、搜索历史和监控健康状态。...
（由于字符限制，完整的 cn_skill_md_content 未全部显示，但应包括完整的翻译版 SKILL.md 内容）
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.
Utility Commands
| Command | Description |
|---|
lint stats | Show summary statistics — entry counts per category, total entries, data size, and earliest activity timestamp |
lint export | Export all data to JSON, CSV, or TXT format. Output file saved to ~/.local/share/lint/export. |
lint search | 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 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
by