The short answer: open Terminal, start typing a commit message or documentation command, press ⌃+⌥+R (Mac) or Ctrl+Alt+R (Linux), speak for 30-90 seconds, and AICHE inserts the formatted text ready to execute.

Typing comprehensive Git commit messages and detailed CLI documentation interrupts development flow, and rushed commits with minimal context create maintenance problems months later.

Open Terminal on your Mac or Linux system.
Begin your command (git commit, echo for README, etc.).
Press your AICHE hotkey to start recording.
Speak your complete message or documentation.
Press the hotkey again - AICHE transcribes and inserts the text.
Complete the command and execute.

Git Commit Messages

Detailed Commit Context

Comprehensive commits document decision-making for future maintainers. Example workflow:

git commit -m "

Then press hotkey and speak: "refactor authentication middleware to use JWT tokens instead of session cookies, removes Express session dependency reducing memory usage by approximately 200MB under load, implements access token with 15 minute expiration and refresh token with 7 day expiration stored in HTTP only cookies, adds token rotation on refresh preventing replay attacks, updates all protected routes to use new JWT verification middleware, maintains backward compatibility by checking for both session and JWT during migration period using feature flag, includes comprehensive tests covering token generation validation refresh and expiration scenarios, updates API documentation with new authentication flow and token refresh endpoint, migration guide added to docs folder for existing deployments"

The detailed commit becomes searchable history when investigating authentication changes months later.

Multi-File Change Explanations

When commits span multiple files, explain the complete picture. Example: "update user profile editing feature across frontend and backend, backend adds new API endpoint PUT slash api slash users slash profile accepting JSON body with name email phone and avatar URL fields, validates email format and phone number using regex patterns, checks email uniqueness excluding current user from query, sanitizes inputs to prevent XSS attacks, updates database using parameterized query, returns updated user object with timestamp, frontend adds profile settings page with React Hook Form for validation, implements file upload for avatar images with preview, adds image cropping modal using React Easy Crop library, shows loading spinner during save operation, displays success toast notification on completion, handles validation errors with inline field messages, adds optimistic UI update for immediate feedback, includes tests for both frontend form submission and backend validation logic".

Complete explanations help code reviewers understand cross-cutting changes without reconstructing context from diffs.

Shell Script Documentation

Script Purpose and Usage

When creating maintenance scripts, document thoroughly. Example for script header:

#!/bin/bash
#

Press hotkey and speak: "automated database backup script for production PostgreSQL server, runs daily via cron job at 2am UTC during low traffic period, creates compressed SQL dump using pg_dump with custom format for efficient compression and selective restore capability, dumps include all schemas tables indexes and sequences but excludes temporary tables prefixed with temp underscore, backup file named with timestamp format database name underscore YYYY MM DD underscore HHMMSS dot sql dot gz for chronological sorting, saves to local backup directory slash var slash backups slash postgres with 30 day retention policy, uploads copy to AWS S3 bucket production dash backups slash database slash using AWS CLI with server side encryption AES 256, logs all operations to slash var slash log slash db backup dot log including start time completion time file size and any errors, sends email notification to ops team on failure using mailx command with error details, requires environment variables DATABASE_URL and S3_BUCKET_NAME to be set before execution, must run as postgres user with read access to database and write access to backup directory"

Comprehensive documentation prevents support issues when operations teams run scripts months later.

Complex Command Explanations

For non-obvious commands, add explanatory comments. Example:

Press hotkey and speak: "find all log files older than 30 days and delete them to free disk space, find command searches slash var slash log directory recursively, name pattern asterisk dot log matches files ending in dot log extension, type f limits to regular files not directories, mtime plus 30 matches files modified more than 30 days ago, delete flag removes matched files, runs with sudo because log directory requires elevated permissions, recommend running with dry run first by removing delete flag and adding print to preview files before deletion, exclude active log files by adding not name pattern current dot log, consider adding to weekly cron job for automated cleanup"

Detailed comments help team members understand and safely modify commands.

README File Creation

Project Documentation

Comprehensive README files need structured content. Example for new project:

echo "

Press hotkey and speak: "project name voice powered task management API, description RESTful API for task management with voice input support built using Node.js Express and PostgreSQL, features include user authentication with JWT tokens, CRUD operations for tasks with title description due date and priority, voice memo attachments stored in AWS S3 with transcription using Whisper API, task sharing and collaboration with permission levels, real time updates using WebSocket connections, installation requirements Node.js 18 or higher PostgreSQL 14 or higher Redis for session storage, clone repository run npm install to install dependencies, copy dot env dot example to dot env and configure database URL Redis URL AWS credentials and JWT secret, run npm run migrate to create database schema, start development server with npm run dev listens on port 3000, API documentation available at localhost 3000 slash api docs using Swagger UI, testing run npm test for unit tests npm run test integration for API tests coverage target 80 percent, deployment supports Docker containerization with provided Dockerfile and docker compose configuration, environment variables documented in dot env dot example file, contribution guidelines follow conventional commits for commit messages, submit pull requests to develop branch with tests and documentation, license MIT see LICENSE file for details"

" > README.md

Speaking README content produces comprehensive documentation without the tedium of typing structured text.

Configuration File Comments

Complex Configuration Explanations

Configuration files benefit from context. Example for nginx.conf:

Press hotkey and speak for comment block: "nginx configuration for production API server, server block listens on port 80 redirects all HTTP traffic to HTTPS using 301 permanent redirect, HTTPS server block listens on 443 with SSL certificate from Let's Encrypt located at slash etc slash letsencrypt slash live slash domain, SSL protocols limited to TLS 1.2 and 1.3 for security, ciphers configured for modern browsers using Mozilla intermediate profile, location block slash api slash proxies to Node.js application server running on localhost port 3000, proxy headers include X-Real-IP X-Forwarded-For and X-Forwarded-Proto for logging client information, proxy timeouts set to 60 seconds to handle long running requests, static files served from slash var slash www slash public with 30 day cache expiration, gzip compression enabled for text based content types, rate limiting configured to 100 requests per minute per IP address using limit_req_zone, access logs written to slash var slash log slash nginx slash access.log using combined format, error logs at warn level written to slash var slash log slash nginx slash error.log"

Detailed configuration comments prevent confusion during server maintenance or troubleshooting.

Result: typing comprehensive Git commit messages and CLI documentation that takes 20 minutes becomes 5 minutes of dictation, and spoken explanations often reveal missing context or edge cases before committing code, improving overall documentation quality.

Do this now: open Terminal, stage some changes with git add, start a commit command, press your hotkey, and spend 60 seconds dictating everything about why the change exists, what it affects, and what future maintainers should know about edge cases or tradeoffs.

AICHE +TTerminal Integration