vendor-bundle-conventions
When editing a vendored third-party bundle, keep the upstream layout
来源信息
- 仓库
- samugit83/cortex
- 最近来源活动
- 2026年9月20日 20:32
- 检测到的 SKILL.md 语言
- 英语
- 星标
- 1
- 分支
- 0
安装方式
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
检查来源文件
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
正在显示 SKILL.md
SKILL.md
来源说明 · 只读预览- name
- vendor-bundle-conventions
- description
- When editing a vendored third-party bundle, keep the upstream layout
- paths
- ["vendor/**","third_party/**"]
# Vendored code
A vendored bundle is a copy of somebody else's release, and the next upgrade is
a straight overwrite.
1. Never reformat a vendored file: the diff against upstream is the only thing
that shows what was changed on purpose.
2. Keep local changes in one patch file beside the bundle, never inline.
3. Record the upstream version in the bundle's own marker file, so an upgrade
can tell what it is replacing.
在 GitHub 查看