원클릭으로
github-qa-labels
Label GitHub issues and PRs found during QA testing. Use when organizing QA findings with proper labels.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Label GitHub issues and PRs found during QA testing. Use when organizing QA findings with proper labels.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Triage and resolve GitHub PR review comments one by one, interactively. Use when the user asks to handle, address, respond to, or resolve PR review comments, or mentions reviewer feedback on a pull request.
Opens a pull request from the current branch using the PR template. Use when the user asks to open a PR, create a pull request, or invokes /open-pr.
Rebuild and restart the internal Storybook UI after changes to internal Storybook code (core, addons, frameworks, renderers, libs, etc.), then optionally display a UI review. Use after editing any package in the Storybook monorepo's code/ directory, or when the user asks to rebuild and/or restart Storybook.
Measure Storybook startup time from spawning `storybook dev` until the first story renders in the browser. Use when the user asks about Storybook boot time, server-ready timing, first story render timing, startup regressions, benchmarking with repeat runs, or comparing Storybook versions or feature flags.
Evaluate a PR's title and description against its actual implementation, then iteratively suggest and apply updates. Use when the user asks to check, fix, or update a PR title or description.
Creates a pull request following Storybook conventions. Use when creating PRs, opening pull requests, or submitting changes for review.
| name | github-qa-labels |
| description | Label GitHub issues and PRs found during QA testing. Use when organizing QA findings with proper labels. |
| allowed-tools | Bash |
When creating or organizing issues/PRs found during QA testing, apply these labels.
Add upgrade:<version> label to track all QA findings for a release:
# Create label if it doesn't exist
gh label create "upgrade:10.2" --repo storybookjs/storybook --color "0E8A16" --description "Issues/PRs found during 10.2 upgrade QA"
# Add to issue/PR
gh issue edit <NUMBER> --repo storybookjs/storybook --add-label "upgrade:10.2"
gh pr edit <NUMBER> --repo storybookjs/storybook --add-label "upgrade:10.2"
Add sev:S1 through sev:S4 to bugs only (not docs or feature requests):
gh issue edit <NUMBER> --repo storybookjs/storybook --add-label "sev:S2"
Severity levels:
| Type | Severity label? |
|---|---|
| Bug (runtime error) | Yes |
| Bug (type error) | Yes |
| Bug (automigrate issue) | Yes |
| Documentation issue | No |
| Feature request | No |
| Enhancement | No |
Label multiple issues at once:
gh issue edit 33524 --repo storybookjs/storybook --add-label "upgrade:10.2" && \
gh issue edit 33527 --repo storybookjs/storybook --add-label "upgrade:10.2" && \
gh pr edit 33526 --repo storybookjs/storybook --add-label "upgrade:10.2"