---
title: "How do I check my AI Code Insights commits?"
canonical_url: "https://docs.getdx.com/knowledgebase/how-do-i-check-my-ai-code-commits/"
md_url: "https://docs.getdx.com/knowledgebase/how-do-i-check-my-ai-code-commits.md"
last_updated: "2026-07-02"
---

# How do I check my AI Code Insights commits?
Use this guide to review your recent commits in DX before responding to an AI Code Insights pilot feedback study. Checking a few commits helps your organization confirm that AI attribution looks accurate before expanding the rollout.

<div style="position: relative; padding-bottom: 59.34065934065934%; height: 0;"><iframe src="https://www.loom.com/embed/ff020f4f35e24462b1e76e4bc43a451f" frameborder="0" webkitallowfullscreen mozallowfullscreen allowfullscreen style="position: absolute; top: 0; left: 0; width: 100%; height: 100%;"></iframe></div>

## Before you begin

You need:

- **Access to DX** through your organization's workspace.
- **AI Code Insights installed** on the machine where you write and commit code.
- **Recent commits** in repositories monitored by DX, preferably commits where you used an AI coding tool.

## Check your commits

1. Open the [AI code percentage](https://docs.getdx.com/reports/ai-code-percentage/) report in DX.
1. Find your team in the breakdown table below the chart.
1. Click the **Overall average** percentage for your team to view the underlying commits.
1. Find 2-3 of your recent commits or PRs where you used an AI coding tool.
1. Review the AI percentage shown for each commit.
1. Compare the percentage in DX against your memory of how much of the code came from AI.

## What to include in your feedback

If the AI percentage looks right, note that in the pilot feedback study.

If a commit is missing or the AI percentage looks inaccurate, include these details in your response:

- **Repository name**
- **PR or commit SHA**
- **AI coding tool used**
- **AI percentage shown in DX**
- **What you expected the AI percentage to be**
- **Any workflow context** that may help explain the result, such as rebasing, resolving merge conflicts, applying stashes, restoring files, or working in a remote development environment

These details help DX investigate attribution issues without guessing which commit or workflow produced the result.

## If you cannot find your commits

If you cannot find your recent commits in the report, include that in the pilot feedback study and share the repository and PR or commit SHA you expected to see.
---

## Sitemap

[Overview of all docs pages](/llms.txt)
