skills.rest
anukkrit149
anukkrit149COMMUNITY
Explore all skills by this author →
Website𝕏@anukkritGitHub

github-qa-labels

Label GitHub issues and pull requests with upgrade and severity tags.

Updated May 26, 2026
Search Tags:#github#qa#github cli#release tracking#severity triage#issue labeling
One-click install
npx skills add https://github.com/anukkrit149/anukkrit-skills --skill github-qa-labels
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-qa-labels
Source: https://github.com/anukkrit149/anukkrit-skills/tree/main/cloud/skills/github-qa-labels
Command: npx skills add https://github.com/anukkrit149/anukkrit-skills --skill github-qa-labels

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams consistently label GitHub issues and pull requests created during QA testing so upgrade findings are easy to track and triage.

Core Features & Use Cases

  • Release-scoped tracking labels: Add an upgrade:<version> label to group all QA findings for a specific release.
  • Bug severity labeling: Apply sev:S1 through sev:S4 only to bugs, with clear definitions for each severity level.
  • Batch labeling workflows: Label multiple issues/PRs efficiently using the GitHub CLI.

Quick Start

Use GitHub CLI to add the appropriate upgrade:10.2 label and (when applicable) sev:S2 to the QA issue or pull request you’re triaging.

Frequently Asked Questions about github-qa-labels

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

FAQPage Schema
How do I label GitHub issues for QA testing and release tracking?▼

GitHub issue labeling for QA testing uses `upgrade:<version>` labels to group release findings and `sev:S1`–`sev:S4` labels for bug severity triage. Applying these consistently enables accurate release tracking across issues and pull requests.

What is the best way to batch label GitHub issues during an upgrade?▼

Batch labeling GitHub issues during an upgrade is handled using GitHub CLI commands to efficiently apply `upgrade:<version>` and `sev:S1`–`sev:S4` labels to multiple issues and pull requests, ensuring consistent release tracking and severity triage.

Can I use GitHub CLI to apply severity labels to pull requests?▼

Yes, GitHub CLI supports applying severity labels to pull requests. You can add bug-only `sev:S1` through `sev:S4` labels to both issues and pull requests created during QA testing to maintain consistent severity triage.

How do I organize QA bugs by severity for triage in GitHub?▼

Organizing QA bugs by severity involves applying `sev:S1` through `sev:S4` labels exclusively to bugs, providing clear definitions for each level to enable effective severity triage and release tracking within your GitHub repository.

Do I need predefined labels before tracking upgrade QA findings in GitHub?▼

Yes, tracking upgrade QA findings requires defining `upgrade:<version>` labels for release scoping and `sev:S1` through `sev:S4` labels for bugs. These must be established in your repository before applying them to issues and pull requests.

Related Skills

Explore More Product & Management Skills→
adiytharpansaadiytharpansa

github

Manage GitHub issues, pull requests, and CI workflows via the gh CLI.

Community
Intermediate
hsch14hsch14

github-triage

Fetch GitHub issue and PR metadata and generate evidence-backed markdown reports.

Community
Advanced
tutur3ututur3u
53

github

Automate GitHub issue, PR, CI, and API tasks via gh CLI.

Official
Intermediate
AlexiosBluffMaraAlexiosBluffMara
2

github-issues

Automate GitHub issue lifecycle management with gh CLI and REST API.

Community
Advanced