القائمة
Create a beachball change file for the current changes. Determines change type (patch/minor) and generates a description from the diff.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Review a PR for correctness, pattern compliance, testing, accessibility, and safety. Produces a confidence score for merge readiness.
Triage newly-filed GitHub issues on the Fluent UI repo (microsoft/fluentui) following the Shield triage guidelines. Fetches open issues labeled `Needs: Triage :mag:` via the `gh` CLI, classifies each (bug vs feature, product area, partner ask, repro quality, a11y), recommends label changes and area-owner assignment, and then applies the approved changes. Use this skill whenever the user asks to triage issues, run shield triage, go through the triage queue, process needs-triage, or any variation -- even if they don't mention "Fluent UI" or "GitHub" explicitly, since that's the project context here.
Visually verify a component by launching its Storybook story and taking a screenshot with playwright-cli. Use after making visual changes to a component.
Run lint on affected packages, parse errors, and auto-fix common issues (design tokens, React.FC, SSR safety, import restrictions)
Quick lookup for a Fluent UI package — path, dependencies, owner team, Nx project details, and relevant docs
Find the matching Fluent UI design token for a hardcoded CSS value (color, spacing, font size, border radius, shadow)
| name | change |
| description | Create a beachball change file for the current changes. Determines change type (patch/minor) and generates a description from the diff. |
| disable-model-invocation | true |
| allowed-tools | Bash Read Grep Glob |
Generate a change file for the current branch's modifications using the repo's beachball setup.
Determine the change type:
patch — bug fixes, internal refactors, test-only changesminor — new features, new exports, new component variantsnone — changes that don't affect the published package (stories, docs, tests only)major without explicit user approvalGenerate a descriptive message following the format: fix(package-name): description or feat(package-name): description
Run the repo's change script to create the change file:
yarn change
This runs beachball change --no-commit (configured in root package.json).
Beachball automatically detects which packages need change files.
For non-interactive usage with a specific type and message:
yarn beachball change --no-commit --type <type> --message "<message>"
Verify the change file was created:
yarn check:change
yarn change or yarn beachball change — never manually create change files