Finishing a Development Branch
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
Import a new upstream release of third-party software into a MidnightBSD vendor branch and merge it into master (and optionally stable branches).
Install Vendor Update
$ npx skills add MidnightBSD/src --skill vendor-update -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install MidnightBSD/src vendor-update --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/MidnightBSD/src.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/vendor-update .claude/skills/vendor-update && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "vendor-update" agent skill from https://github.com/MidnightBSD/src/tree/master/.agents/skills/vendor-update into .claude/skills/vendor-update/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vendor-update", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/MidnightBSD/src/tree/master/.agents/skills/vendor-updateType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add MidnightBSD/src --skill vendor-update -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install MidnightBSD/src vendor-update --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/MidnightBSD/src.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/vendor-update .agents/skills/vendor-update && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "vendor-update" agent skill from https://github.com/MidnightBSD/src/tree/master/.agents/skills/vendor-update into .agents/skills/vendor-update/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vendor-update", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add MidnightBSD/src --skill vendor-update -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install MidnightBSD/src vendor-update --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/MidnightBSD/src.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/vendor-update .cursor/skills/vendor-update && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "vendor-update" agent skill from https://github.com/MidnightBSD/src/tree/master/.agents/skills/vendor-update into .cursor/skills/vendor-update/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vendor-update", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/MidnightBSD/src.git --path .agents/skills/vendor-update--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add MidnightBSD/src --skill vendor-update -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install MidnightBSD/src vendor-update --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/MidnightBSD/src.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/vendor-update .gemini/skills/vendor-update && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "vendor-update" agent skill from https://github.com/MidnightBSD/src/tree/master/.agents/skills/vendor-update into .gemini/skills/vendor-update/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vendor-update", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install MidnightBSD/src vendor-updateInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add MidnightBSD/src --skill vendor-update -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/MidnightBSD/src.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/vendor-update .github/skills/vendor-update && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "vendor-update" agent skill from https://github.com/MidnightBSD/src/tree/master/.agents/skills/vendor-update into .github/skills/vendor-update/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vendor-update", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add MidnightBSD/src --skill vendor-update -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install MidnightBSD/src vendor-update --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/MidnightBSD/src.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/vendor-update .opencode/skills/vendor-update && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "vendor-update" agent skill from https://github.com/MidnightBSD/src/tree/master/.agents/skills/vendor-update into .opencode/skills/vendor-update/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vendor-update", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
vendor-update- GitHub stars
- 114
- Token cost
- ~3.4k tokens
- SKILL.md length
- 1,273 words
- Files
- 1
- Skills in repo
- 5
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Import a new upstream release of third-party software into a MidnightBSD vendor branch and merge it into master (and optionally stable branches).
- Works in 12 steps: Gather information → Read upgrade instructions and Xlist → Ask about FreeBSD patches and local… → …
- Tasks that involve Git workflow
- SKILL.md covers Conventions, Workflow, Vendor branch table reference and Key rules
- Calls git, rsync and gh; reaches github.com
What it does
Vendor Update is an agent skill from MidnightBSD/src. Import a new upstream release of third-party software into a MidnightBSD vendor branch and merge it into master (and optionally stable branches). Handles vendor branch naming, Xlist pruning, tagging, git subtree merge, FreeBSD patch refresh, and stable branch merges — with mandatory user approval before every push, merge, or commit.
Its SKILL.md is about 3.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Git workflow. It works with Git. The repository describes itself as: MidnightBSD OS source code.
When your agent uses it
- Tasks that involve Git workflow
Example prompts
- “/vendor-update”
Workflow steps
12 steps, taken from the step headings in SKILL.md.
- Gather information
- Read upgrade instructions and Xlist
- Ask about FreeBSD patches and local modifications
- Create a worktree for the vendor branch
- Sync new upstream sources into the worktree
- Apply Xlist pruning
- Stage, review, and commit on the vendor branch
- Create an annotated tag
- Push vendor branch and tag
- Merge into master with git subtree
- Handle FreeBSD / local patches (if applicable)
- Push master
What it can do on your machine
Read from SKILL.md and the folder at commit 9450100. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
gitrsyncgh
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
github.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Vendor Update loads about 3.4k tokens when it runs. Until then it costs about 87 tokens; SKILL.md has 1,273 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,273 words (~3,359 tokens).
“Use this skill when you need to import a new upstream release of a third-party software package that lives in a MidnightBSD vendor branch.”
- name
- vendor-update
Files
Just SKILL.md in .agents/skills/vendor-update of MidnightBSD/src.
Open the folder on GitHubat commit 9450100
Compare with similar skills
Vendor Update next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Vendor Update this skillMidnightBSD/src | 114 | — | ~3.4k | Automated safety check: Pass | Custom licence | |
| Finishing a Development Branchobra/superpowers | 297k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Code Design Rationale Investigatorcursor/plugins | 10k | 9 repos | ~2.6k | Automated safety check: Pass | None | |
| Contributor-First PR MergeHKUDS/OpenHarness | 16k | 1 repos | ~847 | Automated safety check: Pass | MIT | |
| Migrate Internal Package into GhostTryGhost/Ghost | 56k | — | ~3.8k | Automated safety check: Pass | MIT | |
| Create Pull Requestcline/cline | 70k | 1 repos | ~1.6k | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
Code Design Rationale Investigator
cursor/plugins
Digs into why code is shaped the way it is by checking git history, pull requests and connected tools in parallel, then reporting a cited read on the tradeoffs.
Contributor-First PR Merge
HKUDS/OpenHarness
Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.
Migrate Internal Package into Ghost
TryGhost/Ghost
Moves a package from another TryGhost repository into Ghost as an internal workspace package while keeping its Git history, with checkpoints for the steps that need an administrator.
Create Pull Request
cline/cline
Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.
Git Merge Conflict Resolver
tailcallhq/forgecode
Resolves Git merge conflicts with a plan-first workflow that keeps both sides' intent, regenerates lock files and backs up deleted-but-modified files.
More from MidnightBSD/src
Security Advisory
MidnightBSD/src
Handle a security fix end to end for MidnightBSD src - triage a FreeBSD security advisory (FreeBSD-SA-) or CVE against this tree, port the fix to master and both stable branches, add the UPDATING…
Update Updating
MidnightBSD/src
Add an entry to the UPDATING file at the repository root. An agent skill from MidnightBSD/src.
Cppcheck Clang Format Precommit
MidnightBSD/src
Run clang-format (prefer clang-format19), clang-tidy19, and cppcheck on staged C/C header changes before committing; auto-format then fail on serious diagnostics.
Splint Post C Sanity
MidnightBSD/src
Run splint after cppcheck/clang-format/clang-tidy precommit sanity to find memory issues, API misuse, and contract violations in staged C code (tolerates older C parser limitations).
Related
Works with
Categories
Questions about Vendor Update
What does Vendor Update do?
Import a new upstream release of third-party software into a MidnightBSD vendor branch and merge it into master (and optionally stable branches). Vendor Update is an agent skill from MidnightBSD/src. Import a new upstream release of third-party software into a MidnightBSD vendor branch and merge it into master (and optionally stable branches).
When should I use Vendor Update?
Vendor Update fits situations like: tasks that involve Git workflow.
How do I install Vendor Update in Claude Code?
Run `npx skills add MidnightBSD/src --skill vendor-update -a claude-code`. Or copy the skill folder (.agents/skills/vendor-update in MidnightBSD/src) into .claude/skills/vendor-update in your project. Claude Code loads it when a task matches its description.
How do I install Vendor Update in Codex?
Run `npx skills add MidnightBSD/src --skill vendor-update -a codex`. Or copy the skill folder (.agents/skills/vendor-update in MidnightBSD/src) into .agents/skills/vendor-update in your project. Codex loads it when a task matches its description.
Can I use Vendor Update in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add MidnightBSD/src --skill vendor-update -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/vendor-update, .gemini/skills/vendor-update, .github/skills/vendor-update and .opencode/skills/vendor-update in your project.
What does Vendor Update need to run?
Going by SKILL.md and its folder, Vendor Update needs the command-line tools its instructions call (git, rsync and gh).
Does Vendor Update access the network?
SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Vendor Update safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Vendor Update use?
Vendor Update has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Vendor Update use?
About 3.4k tokens (SKILL.md is roughly 13k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Vendor Update?
Skills that share tags, products or a category with Vendor Update: Finishing a Development Branch (obra/superpowers, 297k stars), Code Design Rationale Investigator (cursor/plugins, 10k stars), Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars) and Migrate Internal Package into Ghost (TryGhost/Ghost, 56k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Vendor Update?
MidnightBSD (a GitHub organization) maintains it in MidnightBSD/src, which has 114 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 4, 2026.
Source: MidnightBSD/src on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.