maintainer-issue-pr-management

Automate GitHub issue and PR lifecycle management with canonical templates and labels.

5.1k|806|Updated Aug 26, 2025
One-click install
npx skills add https://github.com/vllm-project/semantic-router --skill maintainer-issue-pr-management
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: maintainer-issue-pr-management
Source: https://github.com/vllm-project/semantic-router/tree/main/tools/agent/skills/maintainer/issue-pr-management
Command: npx skills add https://github.com/vllm-project/semantic-router --skill maintainer-issue-pr-management

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Efficiently manage GitHub issues and pull requests by enforcing canonical templates and repository taxonomy, ensuring consistent triage, labeling, and closeout.

Core Features & Use Cases

  • Canonical templates for issues and PRs that standardize titles, descriptions, labels, and acceptance criteria.
  • Triage, labeling, and closeout workflows guided by repository taxonomy to improve response times and maintain quality.
  • Support for actions such as create, update, close, or triage issues/PRs, including scope analysis when needed to determine ownership and tasks.

Quick Start

Ask the agent to create or update an issue or PR using the canonical templates and labels.

Frequently Asked Questions about maintainer-issue-pr-management

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

FAQPage Schema
How do I automate GitHub issue and PR triage for maintainers?

Automate GitHub issue and PR triage by enforcing canonical templates and repository taxonomy, which standardizes titles, descriptions, labels, and acceptance criteria to maintain quality. This streamlines triage, labeling, and closeout workflows for maintainers.

What is the best way to standardize GitHub pull request templates and labels?

Standardize GitHub pull request templates and labels by applying canonical templates that enforce consistent titles, descriptions, and acceptance criteria. This ensures pull requests align with repository taxonomy and labeling rules for higher quality submissions.

How do I analyze codebase scope to determine ownership for GitHub issues?

Analyze codebase scope to determine ownership for GitHub issues by inspecting the repository codebase directly. This scope analysis identifies affected areas and tasks, enabling accurate labeling and ownership assignment during issue triage.

Can I enforce repository taxonomy and labeling rules when creating GitHub issues?

You can enforce repository taxonomy and labeling rules when creating GitHub issues by using automated workflows. These workflows apply canonical templates and standardized labels to ensure every issue meets repository standards upon creation.

What are the limitations of automating GitHub PR lifecycle management?

Automating GitHub PR lifecycle management requires strict adherence to canonical templates and repository taxonomy. Limitations arise if repository standards are undefined or if codebase scope analysis cannot accurately determine ownership for complex pull requests.

Does maintainer issue management work without predefined canonical templates?

Maintainer issue management relies on predefined canonical templates to standardize titles, descriptions, and labels. Without these templates and repository taxonomy, the automated triage, labeling, and closeout workflows cannot enforce consistent quality.