Manage skills across repositories

Beta Qodo treats skills as first-class inputs to its agentic review pipeline. A skill is a markdown capsule (a SKILL.md file plus optional supporting files) stored directly in the repository, encoding context that helps a reviewer evaluate changes: coding standards, architectural decisions, ownership maps, or workflow checklists. At the start of every PR review, Qodo discovers all skills in the repository, filters down to those relevant to the diff, and uses them as live inputs to the review. Findings are cited back to the driving skill by name so the rationale is always traceable. The Skills page, under Review standards in the Qodo portal, is used to manage and validate how skills are applied across repositories. It enables teams to review coverage of standards, identify gaps or inconsistencies in enforcement, and monitor rule activity over time.

​

Before you begin

To use skills, you need:

• At least one skill file to exist under /skills folder in the same repo.
• Admin access to the Qodo portal.

​

How Qodo uses skills

Qodo scans repositories to discover skill files. When a skill can be applied during code review, Qodo identifies it and includes it in the review process, where its review rules are evaluated against the code changes. When a pull request is opened, Qodo evaluates the code against the rules assigned to that repository. Violations are surfaced in the pull request to provide reviewers with context before merging.

​

View skills and repository coverage

​

Find and filter skills

Use the filter bar to find a specific skill, or filter skills by Status, Category, Source and Scope. This helps you quickly locate skills, understand where they are applied, and review their current enforcement status across repositories.

​

View skill coverage and activity

For each skill, the following information is available: This information helps administrators understand which skills are actively contributing to code quality, where they are being enforced, and how widely they are used across the organization.

​

Manage repository assignements

You can change the repositories associated with the skill based on your needs.

1. Log in to the Qodo portal and navigate to Review standards in the left navigation bar.
2. Click the Skills tab.
3. Select a skill in the table.
   The right navigation tab opens.
4. Click Edit. The Skill-related pane opens. Under Scope, the repositories associated with the skill are displayed.
5. Select from list to add or remove repos.
6. Click Save.

​

Deactivate a skill

Skills are automatically activated once Qodo detects, analyzes, and adds them to the Skills list. To stop a skill from being applied during reviews, set its status to Inactive. The skill remains available in the Skills list and can be reactivated at any time.

1. Log in to the Qodo portal and navigate to Review Standards in the left navigation bar.
2. Click the Skills tab.
3. Select a skill in the table.
   The left navigation tab opens.
4. Select the Active drop-down and select Inactive.

​

Understand skill analytics

The analytics section at the top of the Skills page provides a high-level view of rule activity and effectiveness for the selected time period. These metrics help teams understand how frequently rules are applied, measure their effectiveness, and identify opportunities to improve review standards and code quality. A high number of merged violations can indicate that rule violations are reaching the main branch despite being flagged during review. Use this metric to identify which skills are generating the most merged violations and determine whether additional review processes or enforcement measures are needed.

​

Additional resources

• Importing existing rules
• Fetch rules using get-qodo-rules skill.