AI Code Helper
A developer tools toolkit for checking, validating, generating, formatting, linting, explaining, converting, and fixing code from the command line. AI Code Helper provides persistent, file-based logging for each operation with timestamped entries, summary statistics, multi-format export, and full-text search across all records.
Commands
| Command |
Description |
check |
Check code — log check results or view recent entries |
validate |
Validate code or configurations — log validation results or view history |
generate |
Generate code snippets or boilerplate — log generation requests or view recent ones |
format |
Format code — log formatting operations or view recent entries |
lint |
Lint code — log linting results or view recent lint entries |
explain |
Explain code — log explanation requests or view recent explanations |
convert |
Convert between formats or languages — log conversion operations or view history |
template |
Template management — log template operations or view recent templates |
diff |
Diff comparison — log diff results or view recent diffs |
preview |
Preview changes — log preview operations or view recent previews |
fix |
Fix code issues — log fix operations or view recent fixes |
report |
Report generation — log report entries or view recent reports |
stats |
Show summary statistics across all log categories (entry counts, data size, first entry date) |
export <fmt> |
Export all data in json, csv, or txt format to the data directory |
search <term> |
Full-text search across all log files (case-insensitive) |
recent |
Show the 20 most recent entries from the activity history log |
status |
Health check — show version, data directory, total entries, disk usage, and last activity |
help |
Show the full help message with all available commands |
version |
Print the current version string |
Each data command (check, validate, generate, etc.) works in two modes:
- Without arguments: displays the 20 most recent entries from that category
- With arguments: saves the input as a new timestamped entry and reports the total count
Data Storage
All data is stored in plain text files under the data directory:
- Category logs:
$DATA_DIR/<command>.log — one file per command (e.g., check.log, lint.log, generate.log), each entry is timestamp|value
- History log:
$DATA_DIR/history.log — audit trail of every command executed with timestamps
- Export files:
$DATA_DIR/export.<fmt> — generated by the export command in json, csv, or txt format
Default data directory: ~/.local/share/ai-code-helper/
Requirements
- Bash (with
set -euo pipefail support)
- Standard Unix utilities:
grep, cat, date, echo, wc, du, head, tail, basename
- No external dependencies or API keys required
When to Use
- Code review and validation — When you need to log code review findings, validation results, or quality checks for tracking purposes
- Generating boilerplate or snippets — When you want to log code generation requests and keep a history of what was generated and when
- Linting and formatting tracking — When you're running lint or format passes across a codebase and want to log results for each file or module
- Code conversion and migration — When converting code between languages or formats and you need to track what was converted and any issues found
- Bug fixing and diff analysis — When fixing bugs and you want to log the issue, the fix applied, and preview/diff results for future reference
Examples
# Check toolkit status
ai-code-helper status
# Log a code check result
ai-code-helper check "auth.py — missing input validation on login endpoint, 3 issues found"
# Log a validation result
ai-code-helper validate "docker-compose.yml — valid, all services resolve correctly"
# Log a code generation request
ai-code-helper generate "Created REST API boilerplate with FastAPI, includes auth middleware and rate limiting"
# Log a lint pass
ai-code-helper lint "src/ — 12 warnings (unused imports), 0 errors, eslint v8.50"
# Log a code explanation
ai-code-helper explain "Binary search implementation in utils.py — O(log n) time, handles edge cases for empty arrays"
# Log a fix
ai-code-helper fix "Fixed race condition in worker.py — added mutex lock around shared state access"
# View recent lint entries
ai-code-helper lint
# Search across all logs for a specific term
ai-code-helper search "validation"
# Export all data as JSON
ai-code-helper export json
# View summary statistics
ai-code-helper stats
# Show recent activity
ai-code-helper recent
Output
All commands return output to stdout. Export files are written to the data directory:
ai-code-helper export json # → ~/.local/share/ai-code-helper/export.json
ai-code-helper export csv # → ~/.local/share/ai-code-helper/export.csv
ai-code-helper export txt # → ~/.local/share/ai-code-helper/export.txt
Every command execution is logged to $DATA_DIR/history.log for auditing purposes.
Powered by BytesAgain | bytesagain.com | hello@bytesagain.com
1---2name: claude-code3description: Review, validate, and generate code with AI-powered linting. Use when fixing bugs, generating boilerplate, formatting, or running analysis.4---5
6# AI Code Helper
7
8A developer tools toolkit for checking, validating, generating, formatting, linting, explaining, converting, and fixing code from the command line. AI Code Helper provides persistent, file-based logging for each operation with timestamped entries, summary statistics, multi-format export, and full-text search across all records.
9
10## Commands
11
12| Command | Description |
13|---------|-------------|
14| `check` | Check code — log check results or view recent entries |
15| `validate` | Validate code or configurations — log validation results or view history |
16| `generate` | Generate code snippets or boilerplate — log generation requests or view recent ones |
17| `format` | Format code — log formatting operations or view recent entries |
18| `lint` | Lint code — log linting results or view recent lint entries |
19| `explain` | Explain code — log explanation requests or view recent explanations |
20| `convert` | Convert between formats or languages — log conversion operations or view history |
21| `template` | Template management — log template operations or view recent templates |
22| `diff` | Diff comparison — log diff results or view recent diffs |
23| `preview` | Preview changes — log preview operations or view recent previews |
24| `fix` | Fix code issues — log fix operations or view recent fixes |
25| `report` | Report generation — log report entries or view recent reports |
26| `stats` | Show summary statistics across all log categories (entry counts, data size, first entry date) |
27| `export <fmt>` | Export all data in json, csv, or txt format to the data directory |
28| `search <term>` | Full-text search across all log files (case-insensitive) |
29| `recent` | Show the 20 most recent entries from the activity history log |
30| `status` | Health check — show version, data directory, total entries, disk usage, and last activity |
31| `help` | Show the full help message with all available commands |
32| `version` | Print the current version string |
33
34Each data command (check, validate, generate, etc.) works in two modes:
35- **Without arguments**: displays the 20 most recent entries from that category
36- **With arguments**: saves the input as a new timestamped entry and reports the total count
37
38## Data Storage
39
40All data is stored in plain text files under the data directory:
41
42- **Category logs**: `$DATA_DIR/<command>.log` — one file per command (e.g., `check.log`, `lint.log`, `generate.log`), each entry is `timestamp|value`
43- **History log**: `$DATA_DIR/history.log` — audit trail of every command executed with timestamps
44- **Export files**: `$DATA_DIR/export.<fmt>` — generated by the `export` command in json, csv, or txt format
45
46Default data directory: `~/.local/share/ai-code-helper/`
47
48## Requirements
49
50- Bash (with `set -euo pipefail` support)
51- Standard Unix utilities: `grep`, `cat`, `date`, `echo`, `wc`, `du`, `head`, `tail`, `basename`
52- No external dependencies or API keys required
53
54## When to Use
55
561. **Code review and validation** — When you need to log code review findings, validation results, or quality checks for tracking purposes
572. **Generating boilerplate or snippets** — When you want to log code generation requests and keep a history of what was generated and when
583. **Linting and formatting tracking** — When you're running lint or format passes across a codebase and want to log results for each file or module
594. **Code conversion and migration** — When converting code between languages or formats and you need to track what was converted and any issues found
605. **Bug fixing and diff analysis** — When fixing bugs and you want to log the issue, the fix applied, and preview/diff results for future reference
61
62## Examples
63
64```bash
65# Check toolkit status
66ai-code-helper status
67
68# Log a code check result
69ai-code-helper check "auth.py — missing input validation on login endpoint, 3 issues found"
70
71# Log a validation result
72ai-code-helper validate "docker-compose.yml — valid, all services resolve correctly"
73
74# Log a code generation request
75ai-code-helper generate "Created REST API boilerplate with FastAPI, includes auth middleware and rate limiting"
76
77# Log a lint pass
78ai-code-helper lint "src/ — 12 warnings (unused imports), 0 errors, eslint v8.50"
79
80# Log a code explanation
81ai-code-helper explain "Binary search implementation in utils.py — O(log n) time, handles edge cases for empty arrays"
82
83# Log a fix
84ai-code-helper fix "Fixed race condition in worker.py — added mutex lock around shared state access"
85
86# View recent lint entries
87ai-code-helper lint
88
89# Search across all logs for a specific term
90ai-code-helper search "validation"
91
92# Export all data as JSON
93ai-code-helper export json
94
95# View summary statistics
96ai-code-helper stats
97
98# Show recent activity
99ai-code-helper recent
100```
101
102## Output
103
104All commands return output to stdout. Export files are written to the data directory:
105
106```bash
107ai-code-helper export json # → ~/.local/share/ai-code-helper/export.json
108ai-code-helper export csv # → ~/.local/share/ai-code-helper/export.csv
109ai-code-helper export txt # → ~/.local/share/ai-code-helper/export.txt
110```
111
112Every command execution is logged to `$DATA_DIR/history.log` for auditing purposes.
113
114---
115
116Powered by BytesAgain | bytesagain.com | hello@bytesagain.com
bytesagain