Skip to main content
Agentic Security brings Sonar’s OpenAI Daybreak collaboration to Gitar’s code reviews. It catches changes to agent skills that could leak credentials or private code, or remove a required approval step. Gitar reviews instructions together with the scripts they call. Comparing instruction versions can reveal a dropped sign-off step even when the publishing command stays the same. Gitar inspects suspicious content without running it and validates each issue before posting a finding. Agentic Security is included with Enterprise.

What it reviews

Gitar examines changed agent behavior in files such as SKILL.md, AGENTS.md, and CLAUDE.md, along with equivalent agent configuration. It follows relevant local references and helper scripts to understand what the instructions would cause an agent to do. A helper script can change agent behavior even when the instruction file stays the same. Gitar checks the connection between the changed helper and the instructions that invoke it. Ordinary authentication and authorized deployment are legitimate uses of agent instructions. Quoted attack examples or destructive commands need evidence of harmful behavior outside their authorized purpose before Gitar reports an issue.

How review works

During a code review, Gitar inspects the changed instructions and follows the affected local paths. The review focuses on behavior introduced by the PR, including changes made through referenced scripts. Supported issues appear as security findings in the normal code review. Each finding identifies the changed location and explains the path from the instruction to the harmful action. Use the existing feedback and resolution flow to respond to findings. Subsequent reviews can resolve issues after the relevant behavior is corrected.

Inspect security findings

Open Dashboard -> Agentic Security to inspect critical and important security findings across the organization. The page brings together high-impact security findings from Gitar’s code reviews, including the instruction reviewer. The initial view shows open findings across all PR states, with critical findings first. Use the repository and date filters to focus the list. Select Resolved to inspect resolved findings. Resolved findings include acknowledgements without a code fix and exclude dismissed findings. See Providing feedback for how acknowledgements resolve findings. Expand Evidence and suggested fix to read the explanation. The link icon after each title opens the posted finding comment, or the original change when no comment link is available. The severity filter offers Critical, Important, or both. Lower-severity findings remain available in Review findings.

Review coverage

The inspection follows affected instructions and their local references. Unrelated unchanged instructions do not expand the review into an audit of the entire repository. Gitar inspects instructions and supporting code without running the commands or payloads under review. An unavailable reference can limit the conclusions supported by the review.

Code Review

How findings are reported and resolved.

Skills

Define procedures that agents can follow in a repository.