mailpoet/starting-branch
.ai/skills/starting-branch/SKILL.md
ALWAYS use when creating a new branch, starting work on a task, or working on a Linear issue. Handles branch naming, Linear lookup, and branch creation. Do NOT run git switch -c or git checkout -b directly.
$ install --global
skillsauthnpx skillsauth add mailpoet/mailpoet starting-branchInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 24, 2026, 8:40 PM1.7s1 file scanned
SKILL.md
- name:
- starting-branch
- description:
- ALWAYS use when creating a new branch, starting work on a task, or working on a Linear issue. Handles branch naming, Linear lookup, and branch creation. Do NOT run git switch -c or git checkout -b directly.
Starting a Branch
Overview
Creates a properly named Git branch for a Linear issue or task, following the company branch naming conventions.
Step 1: Determine the Branch Name
With a Linear Issue
If the user provides a Linear issue ID (e.g. STOMAIL-1234):
- Fetch the issue using the Linear MCP tool (
get_issue) to get the title and type - Pick the prefix based on issue type:
add/,update/,fix/or any other relevant prefix - Generate the branch name:
<prefix><ISSUE-ID>-<short-description>- Issue ID in the branch name is lowercase (e.g.
stomail-1234) - Description is kebab-case, derived from the issue title
- Keep it short but descriptive
- Example:
fix/stomail-7875-mailpoet-subscription-form-block-reloads-site-editor-iframe
- Issue ID in the branch name is lowercase (e.g.
Without a Linear Issue
If no Linear issue is provided:
- Suggest a branch name based on what the user described
- Ask the user to confirm or provide their own name
Always Confirm
Always present the generated branch name to the user and ask for confirmation before creating it.
Step 2: Create the Branch
Once confirmed, ensure you are on trunk and up to date, then create the branch:
git switch trunk
git pull
git switch -c <branch-name>
Related Skills
mailpoet/writing-tests
development
VerifiedTrustedCommunity
Use when writing, running, or debugging tests. Use when asked to add test coverage, fix a failing test, or run a test suite.
154SKILL.mdUpdated Apr 6, 2026
mailpoet/writing-changelog
testing
VerifiedTrustedCommunity
Use when adding a changelog entry for a branch. Use after completing work on a feature, fix, or improvement that is user-facing.
154SKILL.mdUpdated Apr 6, 2026
mailpoet/reviewing-code
development
VerifiedTrustedCommunity
Use when reviewing pull requests or local code changes. Use when asked to review a PR, review code, test changes, verify implementation quality, or do a code review.
154SKILL.mdUpdated Apr 6, 2026
mailpoet/mailpoet-dev-cycle
development
VerifiedTrustedCommunity
Linting and code quality workflows for MailPoet development (PHP, JS/TS, CSS/SCSS). Use when fixing code style or following the development workflow.
154SKILL.mdUpdated Apr 6, 2026