Jamdesk can now fix your docs build warnings for you. Set AI Fixes to Auto-fix, and after each build Jamdesk commits fixes for broken anchor links, missing page titles and missing page descriptions to your docs branch. Every run has an Undo button, and nothing changes until you switch it on.
The Short Version #
- Auto-fix commits three kinds of fix after each build: broken anchor links, missing titles and missing descriptions.
- You turn it on in Settings or with
jamdesk ai-fix auto, added in CLI 1.1.229. - Each run can be undone from Build History, and an undone fix goes on your ignore list so it doesn’t come back.
- Jamdesk never auto-fixes the build its own commit started, so it can’t loop.
- If you’d rather have Claude Code or another agent apply them,
jamdesk fix --jsongives it the link and description fixes.
You rename a heading, push, and the next build warns you about three anchor links (links to a heading on another page) that now point nowhere. Until now, you fixed them by opening the Fix with AI modal, reading the list and clicking Apply. Jamdesk can now make that commit on its own, and I’ll show what it changes and how to take a run back.
How Do You Turn On Auto-Fix? #
Open your project, click Settings in the sidebar, and pick a mode on the AI Fixes card under General. Auto-fix starts with the next build after you save.
| Mode | What happens |
|---|---|
| Off | Jamdesk doesn't scan builds. The Fix with AI button is hidden. |
| Review first | Jamdesk suggests fixes. You review and apply them in the modal. This is the default. |
| Auto-fix | Jamdesk commits fixes after each build. You can undo each run. |
Auto-fix applies the same fixes as the modal, AI-written page descriptions included, and skips anything you’ve ignored. Each description also becomes the line next to its page in your llms.txt, which is what an agent reads to pick a page. I wrote more about that in Designing Docs for AI Agents.
From the terminal, CLI 1.1.229 adds jamdesk ai-fix. Run it with no argument to see the current setting, or pass off, review or auto:
npm install -g jamdesk
jamdesk ai-fix auto
✓ AI Fixes set to Auto-fix
Jamdesk commits fixes to main after the next build. Pull before you push. Undo runs from the dashboard.
Run jamdesk login first. The command uses the projectId in your docs.json, or the project you pass with --project <id>. The CLI reference lists every option.
What Does an Auto-Fix Change, and How Do You Undo It? #
Each run is one commit to your build branch, authored by autofix@jamdesk.com with the message docs: auto-fix N issues (via Jamdesk). In the run below, Jamdesk fixed two broken anchors in one commit. The build gets an Auto-fixed badge in Build History, and its Auto-fix section lists the changes with a link to the commit on GitHub.
Because Jamdesk writes to your branch, pull before you push, unless you enjoy merge conflicts with a robot. Each auto-fix commit also runs whatever CI you have on that branch. If your docs don’t live on GitHub, Jamdesk saves the fixes to your docs directly.
To take a run back, click Undo on it, then Undo auto-fix. Jamdesk commits the previous version of each file with the message docs: undo Jamdesk auto-fix (via Jamdesk). If you edited a file after the auto-fix, Jamdesk leaves that file alone and lists it for you to undo by hand.
Undone fixes go on your ignore list, so the next build doesn’t apply them again. You can restore them under Ignored in the Fix with AI modal.
The obvious worry with a bot that commits to your repo is a loop of commits fixing commits fixing commits. The auto-fix commit and an undo each start a new build, and Jamdesk never auto-fixes those. If one still has fixable warnings, it’s marked Needs review and waits for you. Each fix is also applied only once, so if you revert one by hand, your revert sticks.
Auto-fix s when a branch protection rule blocks its commit, such as one that requires a reviewed pull request, or when the Jamdesk GitHub App loses write access. The Settings card shows d until you fix the cause and save Auto-fix again.
Can an AI Agent Apply the Fixes Instead? #
Yes. Leave the mode on Review first and let Claude Code or another agent make the edits in your own checkout. The Copy for your AI agent button in the Fix with AI modal copies a plain-text prompt with each fix, its file and line, and the issues to fix by hand.
From the terminal, jamdesk fix --json prints a matching plan from your local files as one JSON document, covering links and descriptions but not titles. It writes no files and asks no questions, so an agent can run it on its own:
{
"version": 1,
"fixes": [
{
"type": "broken_link",
"file": "fr/ai/overview.mdx",
"line": 9,
"oldText": "/fr/ai/selectors#ai-strategies",
"newText": "/fr/ai/selectors#stratégies-ia",
"resolvedBy": "deterministic"
}
],
"unfixable": [],
"notes": []
}
A prompt that works well: “Run jamdesk fix --json, apply the link fixes, and show me the descriptions before you add them.” The JSON format is in Use with an AI agent.
Should You Turn On Auto-Fix? #
Turn it on if you push docs straight to a branch and would rather review a commit than a modal. Stay on Review first if every change goes through a reviewed pull request, since Auto-fix s when a protection rule blocks its commit anyway, or if each commit starts slow CI. The same goes if you want to read every AI-written description before it ships.
Auto-fix doesn’t fix everything a build reports. It skips any warning without one clear fix, such as a link to a page that doesn’t exist, and leaves it under Can’t be fixed automatically for you. A project also gets 1,000 AI requests a day, and a run that hits the limit skips some fixes and says so.
To try it, run jamdesk ai-fix auto in your docs repo and push a change. The Fix with AI docs cover every rule.
Checked against Jamdesk CLI 1.1.229 and the Fix with AI docs on November 1, 2026. Jamdesk wrote this post about its own feature, so if anything here is wrong, email contact@jamdesk.com and we’ll fix it.