aictl

Check each provider for newly released models, compare against the supported set, add any missing ones, and update the per-provider docs and website accordingly

Update README.md, CLAUDE.md, the docs/ tree (ARCH.md, INSTALL.md, USAGE.md, CONFIG.md, PROVIDERS.md, TOOLS.md, EXTENSIONS.md, CODING_AGENT.md, SERVER.md), and the website (website/index.html, website/terminal.html, website/server.html, website/desktop.html) to match the current project state

Write a small, self-contained, locally executable code snippet — bash or python by default.

Connect a Model Context Protocol server to aictl by adding an entry to ~/.aictl/mcp.json. Walks the user through command, args, env, and timeout, then merges the new server into the existing config without disturbing other entries.

Add a lifecycle hook to ~/.aictl/hooks.json. Walks the user through choosing the right event, matcher, command, and timeout, then merges the new entry into the existing config without disturbing other hooks.

Review staged/unstaged changes for correctness, security, and style.

Locate the root cause of a stack trace, panic, or compiler error.

Condense long documents, articles, or URLs into TL;DR + bullets.

Translate between languages with a short note on tone and register.

Generate unit/integration tests for a target file and run them.

Generate a general project statistics report (LOC, commit activity, contributors, etc.) and save it under .claude/reports/stats/ with a timestamp.

Evaluate project performance with focus on Rust and CLI-specific patterns

Evaluate project quality and Rust software development practices

Evaluate project security posture with focus on Rust and CLI-specific risks

Commit staged and unstaged changes with a clear commit message