TAHO Lift

TAHO Lift automates code quality and deployment so you can stay focused on the TAHO integrations you're building. A single command enhances commit messages, updates documentation, and prepares your code for deployment. Everything folds back into your original commit. No extra commits, no clutter. We built Lift on our own team because we noticed a pattern: commit messages get written in a rush, documentation falls behind, and the gap between what the code does and what the docs say keeps growing. Pull requests get harder to review, new teammates take longer to ramp up, and nobody can remember why a configuration changed three months ago. For teams running TAHO in production, that institutional knowledge is critical. Lift closes the gap automatically. When you run lift, two tools execute in sequence on your latest commit. Inky reads your diff and generates a structured commit message with a conventional commit prefix, a summary of what changed and why, and a test plan. If your existing message is already good, Inky preserves it. Doc scans your diff for changes that affect user-facing behavior, APIs, configuration, or workflows, then edits the relevant documentation files in your repository. It only updates existing files and only touches docs when code changes warrant it. Lift is passive by default. It tracks which commits each tool has already processed, so it is safe to run in a post-commit hook or shell alias. If one tool fails, the pipeline continues and reports what happened at the end. Lift runs after you commit: it never rejects your work or blocks your workflow. When you are ready to ship, pass --pr to create or update a pull request directly from the command line. Lift uses layered TOML configuration with sensible defaults embedded in the binary. Override per-user or system-wide. Supports both Git and Sapling with automatic detection. Requires Claude Code and GitHub CLI.