How we verify shortcuts
Where a row on this site comes from, how it is checked by hand before a version is published, what the automated checks add, and what is not checked. Written by Jay, editor. Last revised .
Where a row is allowed to come from
Every row has to trace back to the vendor's own material: its documentation, the application's built-in shortcut list, a command's help output or manual page, official release notes, or, for open-source tools, the keymap or command list in the project's own repository at a tagged release. Blog posts, forum answers and other shortcut sites are not accepted as sources. Each page names the document it was taken from under "Sources and checks", or says that no source is recorded.
Checked by hand before publication
Before a version of the site is published, the editor compares the pages with the vendor's documentation by hand: the key, the action it is listed for, and the operating system it applies to. A row that cannot be found in the vendor's material is corrected or removed. Nothing is copied in bulk from other shortcut sites.
Scripts support that work and do not replace it. They collect the vendor pages, prepare the rows for comparison and run the automated checks listed below.
Row-by-row records
Since October 2026 pages are also being rebuilt from the vendor's current documentation with a record for every row: the vendor page is saved, each row is stored together with the line it came from, and a script rejects any row whose keys do not appear in that line. These pages show "Checked row by row against" with a source and a date, list every source page used, and say how many rows of the earlier version were removed. All 260 tools (43,584 rows) have been rebuilt this way. The update log lists them.
What the automated checks cover
In addition to the hand comparison, a test suite has to pass before any version of the site is published. Among other things it checks that:
- every key shown on a page exists in the dataset, and every row of the dataset appears on its page;
- on rebuilt pages, the keys of each row appear in the saved line of the vendor's text;
- a shortcut quoted in a page's notes or answers matches a row of its table;
- the counts and dates shown on the reference pages equal the data;
- internal links and redirects resolve, and known template filler phrases are rejected.
What is not checked
Shortcuts are not tested by pressing them in each application. A row can therefore be wrong when the vendor's own page is wrong or out of date, or when a binding depends on the keyboard layout, the operating system version or a setting. A comparison by hand can also miss a row. Short descriptions are meant to be in our own words, but on many pages, command-line pages above all, they still follow the vendor's wording closely or are missing; either way a description can misstate what a command does even when the keys are right. If you find such a row, please report it.
Windows and Mac
Where the vendor documents separate Windows and Mac bindings, rebuilt pages show them in separate columns and leave a cell empty when the vendor lists no binding for that system. Where a vendor prints one list and states only a rule (for example "use Cmd in place of Ctrl on a Mac"), the page keeps one column and quotes that rule in a note instead of filling a Mac column. The tables never derive a Mac key by swapping Ctrl for Cmd.
Short pages and group pages
Tools whose documented list is short, up to about a hundred rows, share a page with tools of the same kind: 8 group pages hold 30 tools, each with its own section, table and sources. Their old addresses redirect to the matching section. A tool whose list grows past that size gets a page of its own.
Corrections
Reports come in through the contact page. A confirmed error is fixed in the dataset, which updates the page, the JSON API and the printable sheets together. Checks and structural changes are recorded in the update log.