The code is ready.The PR description shouldn't cost 20 more minutes
Khint puts a PR description generator behind a system-wide shortcut. Type rough change notes into the pull-request form, select them, hit Cmd+Shift+K: a saved AI action rewrites them as a Summary and Test plan and pastes the result back where you were typing. The same palette drafts Conventional Commit messages and triages stack traces, without opening a chat tab.
The writing around the code
is still on you
Your editor's AI helps you write the change; nobody is helping you write aboutthe change. So the PR ships with a one-line description, the reviewer asks what it does, and the commit log reads like a diary of “fix”. The fix isn't another tool with another window: it's making the writing a reflex where it happens. Khint's Agents are saved prompts behind one shortcut: the Dev Daily starter pack ships the three a developer runs daily, a Memory session keeps the context of the branch on hand, and the result lands back in the form you were already filling in.
From pushed branch to reviewable PR, in five moves
Every step runs from the same palette shortcut.
Add the Dev Daily pack: three prompts, zero setup
On the Agents page, open Starter packs and add Dev Daily, a first-party pack with three saved actions: PR description (change notes → a Summary + Test plan body), Commit message (a Conventional Commit from a diff or change note), and Stacktrace triage (an error reduced to cause, likely fix, and where to look). Preview shows each agent running on a sample before you add, and the clone is yours to edit.
Draft the PR body without leaving the PR page
You've pushed the branch and the description box is staring at you. Type your raw notes straight into it: what changed, why, how you checked it. Select them, hit Cmd+Shift+K, and run PR description. The draft is pasted back over your selection as a structured body with a ## Summary of what changed and why and a ## Test plan checklist of how to verify. No chat tab, no copy-paste round trip: the whole point of text actions.
Commit messages that pass review, from the same shortcut
The same move works one step earlier: select a change note or a diff excerpt and run Commit message to get a Conventional Commit:
type(scope): subjectin the imperative, 72 characters max, with a short body when it earns one. If you write commits all day, give the action its own keyboard shortcut in the editor, or pin it in the palette so it sits in a numbered slot you can fire with a single digit.Let a work session hold the “why”
The hardest part of a PR description is remembering why you made the change three days later. Start a Memory session when you pick up the ticket: every action you run and every capture you take lands in it as an entry, compacted into a running summary on your machine. Switch on the session-context option on your PR description action and the draft is written with that record in view: the investigation, the error you triaged Tuesday, not just the lines you selected.
Triage the error on your screen before it derails you
When a failing check or a teammate's screen share shows a stack trace you can't select, run Extract text from the palette: draw a region, Capture puts the text on your clipboard. Paste it, select it, run Stacktrace triage. Three lines come back: cause, likely fix, where to look. If it turns out to be someone else's bug, there's a flow for turning the capture into a ticket instead.
Your notes, your format,
your machine
Because an action is just a prompt you own, the built-in formats bend to your team's: edit the PR description action to add a linked-ticket line or your repo's template sections, and it drafts that way everywhere, forever. And because Khint never connects to your repository, the boundary stays legible: the AI sees the text you selected, and optionally the compacted summary of your active work session, nothing more. Your action history keeps its text locally, and sessions never leave your machine. QA colleagues filing what you fix have their own bug-report flow; if your standup update is also written from yesterday's work, the standup notes flow runs on the same session.
Common questions
Does Khint read my repository or my diff?
No. Khint has no git integration and never indexes your code. An action only ever sees the text you select: a diff excerpt you copied, your own change notes, an error message. If you switch it on per action, it also sees the compacted summary of your active Memory session. You choose what to select; nothing else leaves your machine.
Am I stuck with the built-in PR format?
No. The starter actions are a starting point: the built-in PR description action writes a Summary and Test plan body, and the commit message action follows the Conventional Commits shape. Clone the pack, open any action in the editor, and reword the prompt to match your team's template: different sections, a linked-ticket line, your language. A Generate button drafts a prompt from a one-line description, and Improve refines an existing one in place.
Which apps does this work in?
Anywhere you can select text and paste. The palette is a system-wide shortcut, so the same actions run on a pull-request form in your browser, in your editor's commit box, in a terminal, or in a plain notes file. The result is pasted back where your selection was. There is no separate chat window to copy from.
What does it cost, and what platforms are supported?
Khint is a menu-bar app for macOS and Windows. The free plan includes 10 AI actions and 5 captures per day, no credit card. Your action history keeps its text in a local database on your machine, and Memory sessions never sync to the cloud.
Ship the description with the branch
Free with 10 AI actions and 5 captures per day. No credit card, no repo access: it runs on the text you select.