菜单
PR creation workflow for Sando Design System. Ensures conventional commits, correct branch naming, CI-passing PRs, and well-structured PR bodies. Trigger: When creating a pull request, opening a PR, or preparing changes for review.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | branch-pr |
| description | PR creation workflow for Sando Design System. Ensures conventional commits, correct branch naming, CI-passing PRs, and well-structured PR bodies. Trigger: When creating a pull request, opening a PR, or preparing changes for review. |
| license | Apache-2.0 |
| metadata | {"author":"gentleman-programming","version":"2.0-sando"} |
Use this skill when:
type(scope): descriptiontype/description pattern1. Create branch: type/description (see Branch Naming below)
2. Implement changes with conventional commits
3. Push and open PR using the template at .github/PULL_REQUEST_TEMPLATE.md
4. Verify CI passes (build is blocking)
Branch names MUST match:
^(feat|fix|chore|docs|style|refactor|perf|test|build|ci|revert)\/[a-z0-9._-]+$
Format: type/description — lowercase, no spaces, only a-z0-9._- in description.
| Type | Branch pattern | Example |
|---|---|---|
| Feature | feat/<description> | feat/sando-card-component |
| Bug fix | fix/<description> | fix/focus-ring-input |
| Chore | chore/<description> | chore/update-dependencies |
| Docs | docs/<description> | docs/button-api-reference |
| Style | style/<description> | style/storybook-theme |
| Refactor | refactor/<description> | refactor/extract-flavorable-mixin |
| Performance | perf/<description> | perf/reduce-token-build-time |
| Test | test/<description> | test/add-a11y-coverage |
| Build | build/<description> | build/update-vite-config |
| CI | ci/<description> | ci/add-token-validation |
| Revert | revert/<description> | revert/broken-skeleton-change |
The PR template is at .github/PULL_REQUEST_TEMPLATE.md. Every PR body MUST contain a clear Summary section (1-3 bullet points) describing what was done and why.
The pr.yml workflow runs on every PR:
| Check | Blocking? | What it verifies |
|---|---|---|
Build (pnpm build) | ✅ Yes | Full monorepo builds without errors |
Tests (pnpm test) | ℹ️ Informational | Unit + a11y tests pass |
Lint (pnpm lint) | ℹ️ Informational | TypeScript + ESLint |
The PR cannot merge if build fails. Test and lint failures are reported but non-blocking.
Commit messages MUST match:
^(build|chore|ci|docs|feat|fix|perf|refactor|revert|style|test)(\([a-z0-9\._-]+\))?!?: .+
Format: type(scope): description
type — required: build, chore, ci, docs, feat, fix, perf, refactor, revert, style, test(scope) — optional, use component/package name: button, tokens, storybook, agents! — optional, indicates breaking changedescription — required, imperative mood, lowercaseExamples for Sando:
feat(button): add loading state with spinner
fix(input): correct focus ring visibility in dark mode
refactor(checkbox): extract interaction logic to mixin
docs(api): add JSDoc to sando-select properties
chore(tokens): update amber scale to match new brand
test(badge): add a11y tests for status variant
style(storybook): align preview colors with sando flavor tokens
# Create branch
git checkout -b feat/my-component main
# Push and create PR
git push -u origin feat/my-component
gh pr create --title "feat(scope): description" --body "$(cat .github/PULL_REQUEST_TEMPLATE.md)"
Creates minimal boilerplate structure for new Web Components in Sando Design System following COMPONENT_ARCHITECTURE.md 7-file pattern. Generates only what developer requests - no assumptions, no dead code. Ask first, then scaffold component files, tests, stories based on requirements. <example> User: "Create a new Card component" Assistant: "I'll use the component-creator skill to scaffold the sando-card component with the 7-file pattern." </example> <example> User: "I need a new Accordion component with expand/collapse functionality" Assistant: "I'll use component-creator to scaffold sando-accordion with the specified behavior." </example> <example> User: "Scaffold a new input field component" Assistant: "Using component-creator to generate sando-input with the standard 7-file structure." </example>
Compact guidelines digest for Sando Design System agents. Replaces the full `## 📚 MANDATORY: Read Guidelines Before ANY Work` block that is duplicated across every specialist agent. Provides pre-digested, token- efficient rules organized by agent type. Trigger: inject into sub-agent prompts before task-specific instructions to avoid each agent re-reading full .toon guideline files (saves ~2000-5000 tokens per workflow).
Issue creation workflow for Sando Design System. Creates well-structured GitHub issues for bug reports and feature requests following project conventions. Trigger: When creating a GitHub issue, reporting a bug, or requesting a feature.
Routing table, classification protocol, and ask protocol for the Sando Orchestrator. Extracted from the orchestrator to reduce its context size. Contains the keyword → agent mapping, multi-agent workflow definitions, skill injection reference, and the SDD architectural gate. Trigger: loaded once per session by the orchestrator before any delegation.
Canonical verification protocol for Sando Design System agents. Provides the exact commands, decision trees, and thresholds each specialist agent must run after completing work. Replaces per-agent `<verification>` blocks that are duplicated with slight variations across agents. Trigger: inject into sub-agent prompts so each agent knows exactly what to run and what "done" means.
Sync delta specs to main specs and archive a completed change. Trigger: When the orchestrator launches you to archive a change after implementation and verification.