Ready to supercharge your AI agents?

Install any skill in seconds. Free to start, no credit card required.

Get Started Free →

GitHub QA Labels · storybookjs | DecimalAI

storybookjs/github-qa-labels

NewSkillScoreMaintained

Label GitHub issues and PRs found during QA testing. Use when organizing QA findings with proper labels.

Testingby storybookjs

Links this skill to your agents and keeps it current with the author’s updates.

Automatic

QA & Test Engineering pack

1 · One-time — install the CLI (docs ↗)

pip install decimalai

2 · Get the skill — writes .claude/skills/storybookjs-github-qa-labels/SKILL.md

decimalai skills pull storybookjs-github-qa-labels --out .claude/skills/

No CLI? Get the same file — curl · raw file

curl -fsSL --create-dirs -o .claude/skills/storybookjs-github-qa-labels/SKILL.md https://app.decimal.ai/s/storybookjs-github-qa-labels/SKILL.md

Raw file: /s/storybookjs-github-qa-labels/SKILL.md ↗ · machine-readable summary at /s/storybookjs-github-qa-labels.json ↗

In productionGlobal

how this skill behaves on real traffic · last 30 days

No production data for this skill yet — usage numbers appear here once agents start running it.

Anonymized aggregate across every org using this skill — proof from real production use, not a demo.

Does this skill help? · Benchmark: with vs. withoutsign in to run this on your agents

22 test cases from the publisher’s eval.yaml · each run twice on gemini-3.6-flash — with the skill injected, then without · last run 11h ago

Yes — +82% lift-20% tokens0% turns95% of whole cases pass with skill (21/22)

Test case	Without → With	Effect	Δ tokens	Δ turns
case-01	✗→✓	▲ Improved	-12%	0%
case-02	✗→✓	▲ Improved	-12%	0%
case-03	✗→✓	▲ Improved	-10%	0%
case-04	✗→✓	▲ Improved	-63%	0%
case-05	✗→✓	▲ Improved	-18%	0%

Showing 5 of 22 cases

SkillSafety

✓ 3 of 3 passed

Code scan15 of 15 checks clean

0 critical · 0 warning · 0 info — scanner v5 — 9/23/2026

live_secretremote_code_executionreverse_shelldata_exfiltrationssrf_metadataagent_snoopinganti_refusaldestructive_commandsobfuscated_unicodeunicode_homoglyphopaque_blobsuspicious_urltool_overreachtrigger_abuseprompt_injection_phrasing

IntentSafe

LLM judge · does the skill do what it claims

ContentClean

LLM judge · policy & harmful-content review

Source

Imported

storybookjs / storybook

.agents/skills/github-qa-labels/SKILL.md

View on GitHub ↗

License MITImported 9/23/2026Version v3

Skill contents

SKILL.md

GitHub QA Labels

When creating or organizing issues/PRs found during QA testing, apply these labels.

QA tracking label

Add upgrade:<version> label to track all QA findings for a release:

bash
# 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"

Severity labels

Add sev:S1 through sev:S4 to bugs only (not docs or feature requests):

bash
gh issue edit <NUMBER> --repo storybookjs/storybook --add-label "sev:S2"

Severity levels:

sev:S1: Critical, blocking, no workaround
sev:S2: Significant issue, may have workaround
sev:S3: Moderate issue, workaround exists
sev:S4: Minor issue, edge case, easy workaround

What gets severity labels

| Type | Severity label? | | ----------------------- | --------------- | | Bug (runtime error) | Yes | | Bug (type error) | Yes | | Bug (automigrate issue) | Yes | | Documentation issue | No | | Feature request | No | | Enhancement | No |

Batch labeling

Label multiple issues at once:

bash
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"

Illustrative Want to see what storybookjs/github-qa-labels would put in front of your model? Preview the rendered body and check its trigger phrases — no LLM call, no signup.

Latest benchmark · publisher runVerified

9/27/2026, 06:32 UTC · 22 cases

Lift

+82%

95% vs 14%

Agent turns

0%

1.0 vs 1.0

Tokens

-20%

1,353.95 vs 1,693.18

fail → pass · 19pass → pass · 2pass → fail · 1

Per-case results (22)

Case	Status	Duration (ms)			Turns			Tokens			Tool calls
Case	Status	Without	With	Δ	Without	With	Δ	Without	With	Δ	Without	With	Δ
case-01 I just ran QA testing for the 10.2 release and found a critical runtime crash on issue #34120 that completely blocks usage with no workaround. Can you give me the GitHub CLI commands to tag this issue for QA tracking and assign the appropriate severity?	fail→pass	9,315	5,416	-42%	1	1	0%	1,505	1,323	-12%	0	0	—
case-02 We are triaging QA findings for the 10.2 version update. Issue #34150 is a documentation typo, while issue #34151 is an automigrate bug that causes moderate friction but has a known workaround. Please provide the commands to apply the QA release label and any applicable severity labels to both issues.	fail→pass	7,966	4,253	-47%	1	1	0%	1,329	1,167	-12%	0	0	—
case-03 I need to batch label several items from our 10.2 release QA sweep: issue 33524, issue 33527, and PR 33526. What command chain should I run in GitHub CLI to add the release QA label to all three items at once?	fail→pass	7,887	4,015	-49%	1	1	0%	1,355	1,225	-10%	0	0	—
case-04 During QA on Storybook release 9.1, issue #32001 was filed for a typescript compilation failure in core packages. It is a significant problem affecting build pipelines, though developers can bypass it by casting types to any. Provide the gh CLI command to set the severity label and release QA tracking label on this issue.	fail→pass	15,846	34,757	+119%	1	1	0%	2,973	1,099	-63%	0	0	—
case-05 A user submitted issue #31500 requesting a new addon API during our 10.0 release QA cycle. The issue is high priority for product design. What GitHub CLI command should be used to add the release QA label and severity label to this request?	fail→pass	7,372	3,940	-47%	1	1	0%	1,242	1,019	-18%	0	0	—
case-06 We are starting QA for Storybook version 10.3 and need to create the release tracking label in the storybookjs/storybook repository before tagging issues. Write the GitHub CLI command to create this label with green hex color 0E8A16 and a standard description.	fail→pass	6,934	3,137	-55%	1	1	0%	1,195	986	-17%	0	0	—
case-07 While testing Storybook 10.2, QA found issue #35010: a minor cosmetic alignment glitch on rare dark-mode high-DPI displays with an easy CSS workaround. Give the GitHub CLI command to assign its QA severity and release tracking label.	fail→pass	9,380	4,283	-54%	1	1	0%	1,612	1,214	-25%	0	0	—
case-08 In the 8.5 Storybook release QA sweep, issue #29100 reports a moderate runtime warning in the preview panel that slows down rendering but can be suppressed with a config flag. Provide the command to assign the release tracking label and bug severity.	fail→pass	8,845	3,601	-59%	1	1	0%	1,544	986	-36%	0	0	—
case-09 Issue #33100 in storybookjs/storybook proposes enhancing CLI performance by pre-caching packages during initialization. It was identified during 10.1 QA. Provide the GitHub CLI commands to tag this item with the QA tracking label and appropriate severity tag.	fail→pass	8,564	4,522	-47%	1	1	0%	1,350	1,212	-10%	0	0	—
case-10 PR #33999 contains a bug fix discovered during 10.2 upgrade testing. Show the GitHub CLI command to apply the upgrade QA tracking label to this pull request.	fail→pass	14,927	3,040	-80%	1	1	0%	1,628	856	-47%	0	0	—
case-11 Automigrate failed critically during 10.2 testing on issue #34200, completely blocking migration scripts with no workaround available. Which GitHub CLI command applies the release QA label and severity label?	fail→pass	9,840	5,678	-42%	1	1	0%	1,608	1,519	-6%	0	0	—
case-12 Issue #34205 is an automigrate bug in Storybook 10.2 that skips an optional config parameter on an edge-case framework setup, easily fixed by manual edit. What GitHub CLI command sets the release tracking and severity labels?	fail→pass	15,657	7,703	-51%	1	1	0%	2,451	1,318	-46%	0	0	—
case-13 A QA reviewer opened issue #34300 noting that the Storybook 10.2 docs missing an example for telemetry flags. It's marked as urgent by doc team. Write the GitHub CLI command to label this issue for QA tracking and severity.	fail→pass	5,325	4,193	-21%	1	1	0%	762	1,063	+40%	0	0	—
case-14 We need to execute a single CLI command chain to add QA tracking for release 11.0 to issue 40001, issue 40002, and PR 40003 in storybookjs/storybook. How should this command chain be structured?	fail→pass	15,031	3,790	-75%	1	1	0%	2,828	1,213	-57%	0	0	—
case-15 Issue #34500 is a severe crash in Storybook 10.2 main rendering process, but users can bypass it completely by passing --no-vite flag. Show the GitHub CLI command to apply the release QA label and correct bug severity.	fail→pass	8,728	18,270	+109%	1	1	0%	1,428	1,485	+4%	0	0	—
case-16 Provide the gh CLI command to edit issue #33000 to add the 10.2 upgrade QA tracking label while explicitly ensuring it targets the storybookjs/storybook repository.	fail→pass	4,804	2,325	-52%	1	1	0%	776	803	+3%	0	0	—
case-17 How do we create the QA tracking label for version 9.0 in storybookjs/storybook repository using the GitHub CLI with the standard hex color and description?	fail→pass	22,332	2,887	-87%	1	1	0%	2,163	854	-61%	0	0	—
case-18 We have two bugs from 10.2 QA: issue #34800 is a total crash with no workaround, and issue #34801 is a minor cosmetic glitch in the sidebar. Show the GitHub CLI commands to set severity and release QA labels for both.	fail→pass	7,861	4,670	-41%	1	1	0%	1,220	1,419	+16%	0	0	—
case-19 Issue #34900 is a type error bug with a known workaround, while issue #34901 is an enhancement request filed during 10.2 QA. Provide the CLI commands to apply release QA and severity labels.	fail→pass	11,270	6,868	-39%	1	1	0%	1,995	1,830	-8%	0	0	—
case-20 We want to move issue #34120 from the 'In Progress' column to 'QA Ready' on the Storybook release project board using GitHub CLI. What command should we run?	pass→fail	13,212	14,628	+11%	1	1	0%	2,330	3,051	+31%	0	0	—
case-21 How do I run the end-to-end QA Playwright test suite locally for Storybook 10.2 in the storybookjs/storybook monorepo?	pass→pass	13,759	11,295	-18%	1	1	0%	2,320	2,372	+2%	0	0	—
case-22 Write a template file `.github/PULL_REQUEST_TEMPLATE/qa_fix.md` for contributors submitting QA bug fixes to Storybook.	pass→pass	11,621	8,592	-26%	1	1	0%	1,636	1,773	+8%	0	0	—

These cases were also screened by the skill’s intent / safety pass.See the Trust review ↗Reproduce this benchmark in Colab ↗

How this skill was measured

DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 22 cases were attempted. The headline lift of +82 percentage points is the difference between those two pass rates over the 22 comparable cases. 1 case got worse with the skill loaded, and it is included in that figure.

Model measured: gemini-3.6-flash
Graded by: gemini-3.6-flash
Grading method: judged
Verification: verified
Pass rate without the skill: 13.6%
Pass rate with the skill: 95.5%
Cases attempted: 22
Cases counted toward lift: 22
Cases that regressed: 1
Skill version measured: v3
Run completed: 9/27/2026, 06:32 UTC

Measured example — same prompt, with vs. without the skill · from the benchmark run · case case-01

Prompt

I just ran QA testing for the 10.2 release and found a critical runtime crash on issue #34120 that completely blocks usage with no workaround. Can you give me the GitHub CLI commands to tag this issue for QA tracking and assign the appropriate severity?

Without the skill loaded, the model failed this case. With it loaded, the same prompt on the same model passed. This is one improved case from the latest verified run; every case, including any that regressed, is in the table above.

Show both answers

SkillScore blends 4 signalsno signals yet

BenchmarkRun a verified benchmark with positive lift

Live evalNeeds ≥10 evaluated traces in 30 days

AI ratingNeeds ≥10 rated traces

AdoptionNeeds ≥10 serves across ≥2 orgs in 30 days

No signals yet — run a benchmark or collect evaluated traces to earn a score.

Verified on gemini-3.6-flash · re-tested today

Other measured skills in the registry, with their headline benchmark lift.