Skip to content

Conversation

@yeelam-gordon
Copy link
Contributor

@yeelam-gordon yeelam-gordon commented Jan 27, 2026

This pull request introduces the new "Issue Triage Report" skill for GitHub, providing documentation, licensing, and configuration files to support automated feature area status reports for the Windows App SDK repository. The main changes include the addition of a detailed skill manifest and usage guide, the Apache 2.0 license, and a comprehensive area-to-contact mapping for triage automation.

Skill Documentation and Usage:

  • Added .github/skills/issue-triage-report/SKILL.md, which documents the purpose, triggers, anti-patterns, prerequisites, available scripts, workflows, scoring algorithm, output formats, configuration, troubleshooting, and references for the new "issue-triage-report" skill. This provides clear instructions for generating and using triage and feature area status reports.

Licensing:

  • Introduced .github/skills/issue-triage-report/LICENSE.txt containing the full text of the Apache License 2.0, clarifying the terms under which the skill is distributed and used.

Configuration and Area Ownership:

  • Added .github/skills/issue-triage-report/references/area-contacts.json, a comprehensive mapping of feature areas to primary and secondary contacts, including special handling for triage-only and cross-functional areas. This mapping will be used by the skill to assign responsibility and facilitate triage workflows.

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This pull request introduces a comprehensive "Issue Triage Report" skill for GitHub Copilot, designed to automate the generation of feature area status reports for the Windows App SDK repository. The skill provides engineering teams with tools to identify high-priority issues, track triage status, and highlight items needing immediate attention through a sophisticated multi-factor scoring algorithm.

Changes:

  • Added a complete Agent Skills package with documentation (SKILL.md), licensing (Apache 2.0), and comprehensive usage guides
  • Implemented four PowerShell scripts for report generation, score calculation, and area contact management with configurable scoring weights
  • Created reference documentation detailing the scoring algorithm and area-to-contact mappings for 29 feature areas
  • Provided JSON configuration files and markdown templates to support customizable report generation workflows

Reviewed changes

Copilot reviewed 11 out of 11 changed files in this pull request and generated 22 comments.

Show a summary per file
File Description
.github/skills/issue-triage-report/SKILL.md Main skill manifest with frontmatter, usage instructions, workflows, and scoring reference
.github/skills/issue-triage-report/LICENSE.txt Apache License 2.0 full text for skill distribution
.github/skills/issue-triage-report/scripts/ReportLib.ps1 Shared library functions for scoring, contacts, and utility operations
.github/skills/issue-triage-report/scripts/Get-HighlightScore.ps1 Script to calculate and display priority scores for individual issues
.github/skills/issue-triage-report/scripts/Get-AreaContacts.ps1 Script to retrieve and update area-to-contact mappings
.github/skills/issue-triage-report/scripts/Generate-FeatureAreaReport.ps1 Main report generation script that produces markdown/CSV/JSON outputs
.github/skills/issue-triage-report/scripts/ScoringConfig.json Configurable weights and thresholds for the scoring algorithm
.github/skills/issue-triage-report/references/scoring-algorithm.md Detailed documentation of the multi-factor scoring methodology
.github/skills/issue-triage-report/references/area-contacts.md Human-readable mapping of feature areas to engineering contacts
.github/skills/issue-triage-report/references/area-contacts.json Machine-readable contact mapping with special area designations
.github/skills/issue-triage-report/templates/report-template.md Markdown template showing expected report structure and legend

@yeelam-gordon
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants