vendor-bundle-conventions
When editing a vendored third-party bundle, keep the upstream layout
Source facts
- Repository
- samugit83/cortex
- Last source activity
- September 20, 2026 at 20:32
- Detected SKILL.md language
- English
- Stars
- 1
- Forks
- 0
Install options
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Review the source files
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Showing SKILL.md
SKILL.md
Source instructions · Read-only preview- 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.
View on GitHub