agentic-labeler

Applies area and platform labels to dotnet/maui issues and pull requests.

23.3k|2.0k|Updated May 8, 2020
One-click install
npx skills add https://github.com/dotnet/maui --skill agentic-labeler
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agentic-labeler
Source: https://github.com/dotnet/maui/tree/main/.github/skills/agentic-labeler
Command: npx skills add https://github.com/dotnet/maui --skill agentic-labeler

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintainers of the dotnet/maui repository must manually triage hundreds of issues and pull requests, and inconsistent labeling makes routing, reporting, and ownership tracking unreliable.

Core Features & Use Cases

  • Scoped Label Application: Applies exactly one area-* label and any matching platformWindows/, with special handling for iOS/MacCatalyst compilation overlap and a hard exclusion of platform/tizen.
  • Tie-Breaking and Noop Rules: Resolves ambiguous cases with specificity heuristics (specific control beats generic area) and skips labeling entirely for automated merge PRs, dependency bumps, or unclear content.
  • Use Case: A contributor opens a PR touching CollectionView handlers under /Platforms/Android/; the labeler applies area-controls-collectionview and platform/android without posting comments or touching any other labels.

Quick Start

Ask the agent to label a given dotnet/maui issue or pull request according to the agentic-labeler rules and report which area and platform labels it applied.

Frequently Asked Questions about agentic-labeler

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

FAQPage Schema
How do I automatically label GitHub issues and pull requests by area and platform?

Use the agentic-labeler rules to select exactly one area-* label from the dominant subsystem and platform/* labels from changed-file patterns or explicitly named affected platforms. It runs through the gh-aw workflow, batch evaluation, or interactive Copilot CLI.

How are platform labels inferred from changed files in a .NET MAUI pull request?

Platform labels come from file patterns: *.android.cs or /Platforms/Android/ paths map to platform/android, *.ios.cs maps to both platform/ios and platform/macos, and *.windows.cs maps to platform/windows. Shared cross-platform code receives no platform label.

Does the labeler apply bug, status, or priority labels like t/bug or s/triaged?

No. The labeler applies only area-* and platform/* labels. Kind, status, priority, partner, and performance labels are owned by issue authors, triagers, and other automation such as dotnet-policy-service.

Why is platform/tizen never applied even when Tizen files change?

Tizen is explicitly excluded from this labeler by policy. Tizen files are treated as having no platform suffix, so the labeler picks an area label from the subject matter and applies no platform label for Tizen content.

When does the labeler skip labeling an issue or PR entirely?

It noops on automated inter-branch merge PRs, dependency bump PRs already carrying dependencies and area-infrastructure labels, and items where no area or platform label clearly fits. Bot codeflow mirroring issues are still labeled area-infrastructure.