SKILL.md file and surfaces findings when relevant instructions are not followed.
Skills are reusable, agent-agnostic instruction sets that extend what your AI coding agent can do. Each skill is a plain-text file that describes how to complete a specific engineering task, such as enforcing standards, guiding review behavior, or applying domain-specific practices. Skills follow the open Agent Skills standard and are portable across compatible agents.
How Skill insights are detected
When Qodo reviews a pull request, it identifies skills relevant to the changes and applies the instructions defined in those skills. If a skill includes constraints, expectations, or review guidance, Qodo evaluates whether the changes comply and surfaces a finding when a mismatch is detected. Not every skill affects code review. Skills intended only for code generation or workflow automation may not be used during pull request review.Configure Skill insights
Configure Skill insights in your repository
Add aSKILL.md file to one of these repository directories: .qodo/skills, .claude/skills, .cursor/skills, .agents/skills, or skills. Qodo checks them in that order and uses the first match. This file defines the skills Qodo uses during pull request reviews.
Understand Skill insights in your findings
When Qodo surfaces a finding, it indicates that the code does not align with instructions defined in a repository skill. Skill insights are displayed within findings in the pull request as supporting context that explains why a finding was raised. They appear as a Skill insight label inside the finding, alongside other metadata such as severity or category.
- Why the finding was raised
- Which skill is relevant
- The context behind the feedback
- How it relates to your repository practices
Related resources
- Anatomy of a Qodo Code Review: The parts of the review comment and how to read them.
- Manage skills across repositories: View all skills used in code review across your repositories.