> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.islo.dev/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.islo.dev/_mcp/server.

# Bug fix

> Move from a confirmed bug to a pull request, or repair failing CI on an existing pull request.

Choose the starting point that matches the work you have.

| Starting point                           | Line                                                                        | Result                                                |
| ---------------------------------------- | --------------------------------------------------------------------------- | ----------------------------------------------------- |
| A bug report without a confirmed cause   | [Triage a bug](/concepts/issue-triage) (`triage-bug`)                       | Verified diagnosis and a fix ticket; no code changes  |
| A planned Linear ticket for the fix      | [Ship a planned ticket](/concepts/feature-delivery) (`ship-planned-ticket`) | Pull request, review, and verification                |
| An existing pull request with failing CI | Dashboard **ci-fix** template                                               | Fixes on the pull request branch and a run to inspect |

For a new bug, first use **Triage a bug** to collect evidence. Review the resulting Linear ticket, then use **Ship a planned ticket** with the `Islo` label to implement it. The same delivery Line works for planned bug fixes and features.

For failing CI, open **Lines → New line** in the dashboard and choose **ci-fix**. Connect GitHub, enter the repository and pull request number, and deploy. The template starts a manual run. [Deploy your first Line](/getting-started/quick-start) shows the dashboard fields and where to inspect the run.

If your fix needs different checks or stages, [build a custom Line](/concepts/custom-lines).