Skip to main content
Gitar works directly in your PR interface. All interactions, status updates, and approvals happen right where you code — no context switching to external dashboards.
Add the gitar-skip label to any PR to skip all Gitar processing (code review, CI analysis, rule evaluation) for that PR.

​
Dashboard Comment

When a new PR is created, Gitar posts a comment used for status updates and controls. Gitar posts status updates about its activity by updating this comment in realtime. You can control default behavior like enabling automatic CI failure fixing etc.

​
CI Failure Analysis

When CI fails, Gitar automatically analyzes the failure, identifies the root cause, and can push a fix. See CI Failure Analysis for details.

​
Interactive Commands

Comment on a PR to interact with Gitar — request fixes, ask questions, or toggle settings. See Commands & Interactions for the full list.

​
Troubleshooting

If Gitar isn’t responding to your comments, verify:
  • Your comment addresses Gitar — start with Gitar (case-insensitive), @gitar, or @gitar-bot (GitHub). Replies to one of Gitar’s own comments work without a prefix.
  • You have write access to the repository (only users with write access can trigger Gitar responses)
  • If you want Gitar to push a fix automatically, auto-apply is enabled on the PR — toggle it with gitar auto-apply:on
If CI continues to fail after Gitar’s attempts:
  • Multiple iterations may be needed — complex CI failures sometimes require several rounds of fixes
  • Gitar will automatically iterate on new CI failures to resolve them and make CI green
  • Provide additional context by commenting with more details about the specific failure
  • Gitar maintains full context of your PR throughout its lifetime, so you can comment to steer behavior at any time
  • Consider configuring repository instructions on how to best use your build environments and development practices by giving it custom AI rules