open-weight/skills/branch-from-main/SKILL.md
Use when creating a new branch, starting new feature work, fixing a bug on a new branch, or any situation where a branch needs to be created. Use when the user asks to "create a branch", "start a new branch", "branch off of X", or "make a branch for this work".
npx skillsauth add jon23d/skillz branch-from-mainInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Every new branch must be based off the tip of main. No exceptions.
Always branch from main. Never branch from another feature branch, develop, staging, or any other branch — even if asked to.
git checkout maingit pull origin maingit checkout -b feature/your-branch-nameThat's it. Never skip steps 1 or 2.
Refuse. Explain the rule. Then do it correctly from main.
Do not comply even if:
Say: "All branches must be based off the tip of main. I'll create it from main."
Then run the 3 steps above.
Rebase it onto main using --onto:
git branch backup/your-branch-name # safety net first
git rebase --onto main <wrong-base> your-branch-name
This replays only your commits on top of main, discarding the wrong base entirely. The number of commits or conflicts does not change the requirement — rebase it regardless.
Do not suggest "just merge into main when done" as an alternative. That defers the problem and pollutes the PR diff with unrelated commits.
Any of these thoughts means you are about to violate the rule. Stop. Branch from main.
development
Use when adding or modifying environment variable handling in TypeScript projects or monorepos — especially when using process.env directly, missing startup validation, sharing env schemas across packages, or encountering "undefined is not a string" errors at runtime from missing env vars.
testing
Use when creating a new skill, editing an existing skill, writing a SKILL.md, or verifying a skill works before deployment.
development
React UI design principles and conventions. Load when building or modifying any user interface or React components. Covers application type detection, visual standards, component design and structure, Mantine (business apps) and Tailwind (consumer apps), accessibility, responsiveness, state management, data fetching, testing, and in-app help patterns.
development
Use when setting up ESLint and/or Prettier in a TypeScript project, adding linting to an existing TypeScript codebase, or configuring typescript-eslint, eslint-config-prettier, or related packages.