Fix with AI
Review and apply AI-suggested fixes for broken links and missing page descriptions from your Jamdesk build dashboard, committed to GitHub for you.
Jamdesk can repair many of the broken links and missing page descriptions a build reports. The Fix with AI button reads those build warnings and proposes an edit for each one. It commits the fixes you approve to your connected GitHub repository. The commit starts a new build.
The jamdesk fix CLI command does the same in your terminal. It writes to your working copy and leaves the commit to you.
What it fixes
Fix with AI repairs three kinds of build warning:
- Broken internal links: a link fragment that points at a heading which no longer exists on the target page, such as a typo (
#instalation→#installation), or a translated page whose heading was renamed. - Missing page descriptions: a page with no
descriptionin its frontmatter. Jamdesk writes a short summary from the page content for you to review. - Missing page titles: a page with no title gets a suggested one from the page content, for you to review.
It proposes a change only when it can resolve the target with confidence. It lists anything ambiguous separately for you to fix by hand.
Fix with AI makes up to 1,000 AI requests per project in a 24-hour period. Results for pages that haven't changed are reused and don't count toward the limit.
The fixable count is not the same as the warning count. A build can show five warnings while Fix with AI offers to repair three of them. The other two have no unambiguous fix.
Choose what happens
The AI Fixes setting decides what Jamdesk does with fixable warnings. To change it, click Settings in the sidebar and find the AI Fixes card under General.
| 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. |
How Auto-fix works
Auto-fix applies the same fixes as the modal, AI-written descriptions included. It skips anything you ignored. It starts with the next build after you save the setting.
After a build, Jamdesk commits the fixes to the project's build branch. The commit message is docs: auto-fix 3 issues (via Jamdesk) and the author is Jamdesk. The build shows an Auto-fixed badge in Build History. For docs without GitHub, Jamdesk saves the fixes to your docs instead.
Jamdesk commits to your branch. Pull before you push. Each auto-fix commit also runs any CI your repository has on that branch.
What to expect from each run:
- Jamdesk doesn't auto-fix the build of its own commit. If that build still has fixable warnings, it shows Needs review and you apply them from the modal.
- A fix is applied once. If you revert it, Jamdesk doesn't apply it again, so your revert sticks. A fix that comes back shows under Needs review.
- Builds whose warnings didn't change since the last run are skipped.
- Auto-fix pauses when the build branch is protected or the Jamdesk GitHub App loses write access. The card shows Paused. Fix the cause, then save Auto-fix again.
- Daily AI limits are the same as for the modal. When a project reaches the limit, the run skips some fixes and says so.
- A new description changes the page, so the next translation run translates that page again.
Prerequisites
- A connected GitHub repository for the project.
- Write access for the Jamdesk GitHub App to commit the fixes. The modal shows a Grant access link to GitHub when access is missing.
- A completed build that carries broken-link or missing-description warnings.
Find the banner
Open your project and scroll to Build History on the Project Home page. A banner with a count and a Fix with AI button appears above the build list when your latest build has fixable issues.
The banner appears only on your newest completed build. Fixes always apply to the current state of your docs.
Review and apply the fixes
Click Fix with AI. The modal opens. The AI agent takes a few seconds to review your docs and build a fix plan.
Fixes are grouped by type. Broken links shows each rewritten anchor. Missing descriptions shows the suggested summary for each page. Missing titles shows the proposed title. Clear the checkbox on anything to skip it this time. Use the ignore button to silence a recommendation for good. Issues with no clear fix appear under Can't be fixed automatically for you to fix by hand.
Click Apply fixes. Jamdesk commits the selected changes to your connected branch with the message docs: apply AI-suggested fixes (via Jamdesk) and starts a new build.
Watch the new build in Build History. The fixed warnings are gone once it goes live. Anything left is either a warning Fix with AI could not resolve or a new issue from the latest content.
Applying writes a real commit to your repository. Review or revert it on GitHub like any other commit.
When some issues can't be fixed
The modal lists warnings with no clear fix under a separate heading and leaves them alone. Common reasons:
- A broken link whose target page or heading doesn't exist anywhere.
- A navigation entry with no matching source file.
- A page where the agent could not generate a description.
These need a manual edit. Open the page in the editor or your code editor. Correct the link or add the description. Push to rebuild.
Ignore recommendations
Some warnings aren't worth acting on: a link you broke on purpose, or a stub page that needs no description. Unchecking a fix only skips it once. Ignoring removes it from the count until you restore it.
Every row in the modal has an ignore button, fixable or not. Clicking it moves the item to a collapsed Ignored section at the bottom. The banner count on the Project Home page drops to match after you close the modal. The matching warnings disappear from Build History on the current build and every build after it. Ignore all does the same for everything still listed.
How ignores behave:
- Shared and persistent: ignores apply to the whole project. Every member sees the same list. It carries across builds. Jamdesk matches each warning by its content, not its line number. Editing other parts of the page won't bring an ignored item back.
- Restoring: expand the Ignored section and click Restore on any item. Ignoring everything on a build hides the banner. A small "N ignored recommendations" link under Build History then reopens the modal.
- Changed warnings come back: an ignored item returns as a new recommendation when the underlying issue changes, for example when the broken link now points somewhere else.
Undo an auto-fix
Every auto-fix run has an Undo button. Open the build in Build History and find the Auto-fix section. It lists what Jamdesk changed and links to the commit. Click Undo, then Undo auto-fix to confirm.
Jamdesk commits the previous version of the files to your branch with the message docs: undo Jamdesk auto-fix (via Jamdesk). If a file changed after the auto-fix, Jamdesk skips it and lists it. Undo those files by hand.
Undone fixes are ignored. Their warnings are hidden, and Jamdesk doesn't apply them again. To bring them back, open Fix with AI and restore them under Ignored.
Hand fixes to your AI agent
You can let a coding agent such as Claude Code make the edits in your repository. In the Fix with AI modal, click Copy for your AI agent. Jamdesk copies a plain-text prompt that lists each suggested fix with its file and line, plus the issues to fix by hand. Ignored items are left out. Paste the prompt into your agent.
From the terminal, jamdesk fix --json gives an agent the same list as JSON. See Use with an AI agent.
Fix with AI vs. the CLI
The dashboard and the CLI fix broken-link anchors. They differ in where they run and how the change lands.
| Fix with AI (dashboard) | jamdesk fix (CLI) | |
|---|---|---|
| Runs | In the dashboard, on a build | In your terminal, against local files |
| Fixes | Broken links, missing descriptions and missing titles | Broken-link anchors, plus missing descriptions with AI |
| Commit | Commits to your branch for you | Writes local files; you commit |
| Trigger | One click on the build banner | jamdesk fix |
Use the dashboard flow for a quick repair without leaving Jamdesk. Use the CLI when you want the changes in your working copy first, for example to bundle them with other edits.
Setting AI Fixes to Off stops the dashboard scans. jamdesk fix still runs on your computer. To change the setting from the terminal, run jamdesk ai-fix with off, review or auto:
jamdesk ai-fix auto