Menu
Create feature branches for all work. Use when creating branches, checking out, or pushing. Prevents accidental push to main.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | feature-branch |
| description | Create feature branches for all work. Use when creating branches, checking out, or pushing. Prevents accidental push to main. |
All work must be on feature branches. Never commit directly to main.
Branch format: <type>/W-XXXXX-short-description (e.g. feature/W-23006798-implementor-references, fix/..., chore/...). Include a short description after the work item number.
git fetch origin main
git checkout main
git pull
git checkout -b feature/W-XXXXX-short-description
# ... work, commit ...
git push -u origin feature/W-XXXXX-short-description
Or, branch from remote without tracking it:
git fetch origin main
git checkout -b feature/W-XXXXX-short-description origin/main --no-track
Never git checkout -b feature/W-XXXXX origin/main without --no-track.
That sets the new branch to track origin/main. A bare git push would then push to main instead of creating a remote feature branch.
--no-track when branching from origin/<base>, or branch from local <base> after pullgit push -u origin feature/W-XXXXXApex Language Server data architecture — type sources, worker topology, and data ownership. Use when working on type resolution, worker communication, resource loading, hover, definition, diagnostics, or any code in apex-ls/src/server/ or apex-parser-ast/src/symbols/.
Numbering convention for ordering GUS work items within an epic. Numeric prefixes in Subject__c express sequencing (do X before Y) and parallelism. Use when planning an epic, when the user states a dependency between work items, or when asked what's unblocked/ready in an epic.
Enforces Effect-TS patterns for services, errors, layers, and atoms. Use when writing code with Effect.Service, Schema.TaggedError, Layer composition, or effect-atom React components.
Interact with the Gus Salesforce org via CLI (sf). Query, create, update work items; query team epics. Use when user mentions Gus, work items, epics, or GUS/Git2Gus workflows.
Guidelines for package.json files in packages
writing, running, and debugging Playwright tests. working with their output from github actions