القائمة
Create a changeset file for versioning packages. Use when the user wants to document changes for release, create a changelog entry, or bump package versions.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
How to build UI in this repo — the bui (@backstage/ui) design system vs legacy @backstage/core-components + MUI v4, which to reach for, and how to read Backstage Storybook component/story source. Use when creating or changing pages, cards, layouts, buttons, or any frontend component.
Patterns for implementing tables. Covers the bui Table ('@backstage/ui') — preferred for new, simple tables — and the feature-rich '@backstage/core-components' Table with search, filtering, and column-visibility persistence.
Common rules for working with this repository
Read, classify, and triage Sentry issues for this Backstage app, propose mitigations, and decide their disposition (fix, resolve, mute, or escalate). Use when given a Sentry issue URL (giantswarm.sentry.io/issues/...), asked to investigate a Sentry error/exception/CSP violation, asked why an image/script/style/font was blocked on a page, or asked to mute/ignore noisy Sentry issues.
Build Backstage backend plugins with createBackendPlugin and core services: DI, httpRouter, secure-by-default auth, Knex DB, routes, testing. Use for APIs and background jobs.
Build Backstage frontend plugins with the new Frontend System: createFrontendPlugin, blueprints, routes, Utility APIs, testing. Use for pages, nav, entity content, or cards.
| name | changeset |
| description | Create a changeset file for versioning packages. Use when the user wants to document changes for release, create a changelog entry, or bump package versions. |
| user-invocable | true |
| allowed-tools | Read, Write, Glob, Grep, AskUserQuestion |
Create changeset files for projects using @changesets/cli.
ls .changeset/*.md 2>/dev/null | head -5find packages plugins -maxdepth 2 -name package.json -exec jq -r .name {} \; 2>/dev/null | sortpackages/* and plugins/*package.json files in workspace directories and extract namesapp, backendUse AskUserQuestion tool to ask:
Generate a unique file name for the changeset by running the script .claude/skills/changeset/generate-file-name.sh.
Create the file with the name obtained in step 3 with the following content:
---
'package-name': patch
---
Summary description here.
Rules:
app, backend, @giantswarm/backstage-plugin-gs)yarn changeset version.changeset/ directory if missingDisplay: