菜单
Open a pull request for the Unovis repo with the project's conventions — correct branch off `main`, the standard commit grouping, and the checklist-style PR body used by the maintainers. Use when asked to open/create/submit a pull request, prepare a branch for review, or write a PR description in this repository.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/f5/unovis --skill open-pr命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
| name | open-pr |
| description | Open a pull request for the Unovis repo with the project's conventions — correct branch off `main`, the standard commit grouping, and the checklist-style PR body used by the maintainers. Use when asked to open/create/submit a pull request, prepare a branch for review, or write a PR description in this repository. |
Mirror the maintainers' real PRs: #821 Boxplot and #812 RadialBar.
main; never commit directly to main.feat/boxplot, fix/crosshair-threshold.Signed-off-by requirement.Split the work into logical commits (see /commit for the message format). For a new component
the maintainers use this 4-commit grouping:
Component | <Name>: New component — the packages/ts core (config, index, style, types, modules)
plus its export wiring and registry entry.Dev | Examples: <Name> examples (or Dev | Examples | <Name>: ...) — the packages/dev pages.Misc: Framework integrations — the regenerated wrappers across React/Angular/Svelte/Vue/Solid.Website: <Name> docs and gallery example — the .mdx doc + packages/shared/examples gallery
entry + previews.For smaller changes, one well-scoped commit is fine — keep core/dev/website/wrapper concerns in separate commits when they coexist.
New Component: <Name> (<milestone>) — e.g. New Component: Boxplot (1.7).Type | Scope: Subject spirit isn't required for the
title, but keep it specific.Use the maintainers' checklist template (tick what applies):
Adding a new `<Name>` <XY/Core/standalone> component
- [x] Dev examples
- [x] Wrappers
- [x] Gallery example
- [x] Docs
<!-- Light + dark screenshots and/or a short screen recording of the component -->
For non-component PRs, write a short summary of what changed and why, and keep a checklist of the surfaces touched (core / dev / docs / wrappers) when relevant.
git push -u origin <branch>
gh pr create --base main --title "New Component: <Name> (<milestone>)" --body "$(cat <<'EOF'
Adding a new `<Name>` XY component
- [x] Dev examples
- [x] Wrappers
- [x] Gallery example
- [x] Docs
EOF
)"
pnpm lint is clean and the build passes (CI runs
pnpm build && pnpm build:dev).Add a new visualization component to Unovis end to end — the TypeScript core, the shared registry, the generated framework wrappers, a dev example, a gallery example, and docs. Use when asked to add/create a new component, chart type, plot, or diagram to the library, or to wire an existing core component through to the framework wrappers.
Add an example to the Unovis gallery — a per-framework example directory under packages/shared/examples, registered in examples-list.tsx, with light/dark previews. Use when asked to add a gallery example, showcase a chart in the gallery, or create the gallery entry that accompanies a new component.
Create git commits in the Unovis repo that pass its commitlint rules. Unovis uses a CUSTOM commit format (`Type | Scope | Subscope: Sentence-case subject`), NOT Conventional Commits, so `feat:`/`fix:` will be rejected by the commit-msg hook. Use this whenever staging and committing changes, writing or rewriting a commit message, splitting work into commits, or recovering from a commitlint rejection in this repository.
基于 SOC 职业分类
