Redirect legacy /mb-pull requests to the /mb-update workflow.
npx skills add https://github.com/noontide-co/mainbranch --skill mb-pull
Please help me install this Agent Skill. Skill: mb-pull Source: https://github.com/noontide-co/mainbranch/tree/main/.claude/skills/mb-pull Command: npx skills add https://github.com/noontide-co/mainbranch --skill mb-pull
This skill replaces the legacy /mb-pull usage with the current /mb-update pathway to preserve behavior for users on older prompts.
Ask the agent to perform the legacy /mb-pull, which runs the same mb update workflow.
High-intent search queries and answers about installing and using this skill.
When you use mb-pull, it redirects to the mb-update workflow and runs mb update --repo . --json. This ensures older prompts remain compatible while executing the exact same update logic and returning identical results as the current pathway.
There is no functional difference between mb-pull and mb-update. The mb-pull command acts purely as a legacy alias, routing requests directly to the mb-update workflow to execute the same underlying update command and results handling.
You do not need to manually migrate old prompts from mb-pull to mb-update. The alias automatically intercepts the legacy language and seamlessly applies the current mb update workflow, preserving behavior without requiring prompt modifications.
Yes, you can use mb-pull to pull latest changes using the old Main Branch language. It explicitly recognizes this legacy phrasing and maps it directly to the current mb update invocation for your local repository.
darelabs-techManage DARE-compatible skill units in a project directory.
lorenzoveniceAutomate NanoClaw updates from upstream with merge conflict resolution.
plot-pmAutomate Plot workflow delivery with plan verification and branch status updates.
kimasplundAssess pre-coding confidence with a five-category checklist and verdict.
