pr-changeset-check
Check if PR has appropriate changesets before creating
- License 许可
- MIT
- 最近更新
- 2026-11-15
- Stars
- ★ 3
- Forks
- 1
01 前言 Front Matter
- name
- pr-changeset-check
- description
- Check if PR has appropriate changesets before creating
- user-invocable
- false
02 资源文件 23
- 资产文件assets/configmap_template.yaml1.4 KB
- 资产文件assets/deployment_template.yaml2.2 KB
- 资产文件assets/hpa_template.yaml806 B
- 资产文件assets/ingress_template.yaml1.7 KB
- 资产文件assets/networkpolicy_template.yaml1.8 KB
- 资产文件assets/pdb_template.yaml1.8 KB
- 资产文件assets/README.md896 B
- 资产文件assets/secret_template.yaml1.6 KB
- 资产文件assets/service_template.yaml1.5 KB
- 资产文件assets/statefulset_template.yaml3.8 KB
- 参考文档config/settings.yaml1.9 KB
- 参考文档references/errors.md12.0 KB
- 参考文档references/examples.md16.1 KB
- 参考文档references/kubernetes_api_reference.md9.2 KB
- 参考文档references/kubernetes_deployment_best_practices.md8.4 KB
- 参考文档references/README.md614 B
- 参考文档references/security_best_practices.md9.2 KB
- 参考文档references/troubleshooting_guide.md9.6 KB
- 脚本scripts/apply_manifest.sh9.4 KB
- 脚本scripts/delete_manifest.sh10.1 KB
- 脚本scripts/get_resource_status.sh11.3 KB
- 脚本scripts/README.md430 B
- 脚本scripts/validate_manifest.sh9.0 KB
03 SKILL.md 正文
Before creating a PR, verify changesets exist for modified packages.
- Check which packages changed:
git diff main --stat | grep packages/ - Check existing changesets:
ls .changeset/*.md - If packages changed but no changeset exists, remind user to create one
- Skip packages in ignore list: dill-docs, repopo-docs
04 同仓库更多 Skills
unslop
Cut AI tells from any writing.
storytelling
Make sure all prose sentences contribute to a coherent narrative, forming a small story rather than a series of disconnected statements.
stop-slop
Remove AI writing patterns from prose. Use when drafting, editing, or reviewing text to eliminate predictable AI tells.
prose-banlist
A skill that bans certain phrases from being used in prose writing.
ponytail
Lazy senior dev mode: the smallest change that fully solves the task, and a reply a busy human understands in one read. Use on any coding task (writing, fixing, refactoring, reviewing, choosing dependencies) and when the user says "ponytail", "be lazy", "simplest solution", "yagni", or complains about over-engineering or bloat. Levels: lite, full (default), ultra.
ponytail-review
Quality review of a change: is the logic right, is it safe, does it hold under real load, is risky code tested, is it fast enough, and is every line needed. Reads the connected code, not only the diff. Each finding is explained in plain English. Use for "review this", "code review", "review the last commit", "review my PR", "is this over-engineered", /ponytail-review.