owners

Query Gerrit to identify code components and their owners for files.

2.3k|552|Updated Feb 20, 2019
One-click install
npx skills add https://github.com/Checkmk/checkmk --skill owners
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: owners
Source: https://github.com/Checkmk/checkmk/tree/main/.github/skills/owners
Command: npx skills add https://github.com/Checkmk/checkmk --skill owners

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps you quickly identify the responsible owners and the specific components associated with files within the Checkmk codebase.

Core Features & Use Cases

  • Component Identification: Determine which component a given file belongs to.
  • Owner Lookup: Find the designated owner(s) for specific files or components.
  • Component Listing: Get a comprehensive list of all defined components and their members.
  • Use Case: When a bug is reported for a specific file, you can use this Skill to immediately find the owner responsible for that code section.

Quick Start

Use the owners skill to find the owner for the file '/path/to/your/file.py'.

Frequently Asked Questions about owners

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find code owners for a specific file in a Gerrit repository?

To find code owners for a specific file, you can query the Gerrit code review system to identify the designated component and its associated members responsible for that file path.

What is code ownership mapping and how does it help with code review assignment?

Code ownership mapping links specific files to designated components and their members, allowing you to accurately route code review assignments and clarify responsibility within the project structure.

How do I list all defined components and their members in the Checkmk codebase?

You can list all defined components and their members by querying the repository structure, which provides a comprehensive overview of project organization for the entire codebase.

Can I use component mapping to identify who owns a buggy file?

Yes, when a bug is reported for a specific file, component mapping queries the codebase to immediately find the designated owner responsible for that code section.

Does the code ownership query work for the entire codebase or just individual files?

The code ownership query supports both individual file lookups and entire codebase analysis, allowing you to identify specific file owners or list all components across the whole project.