pkuppens/plan-branch-strategy
skills/plan-branch-strategy/SKILL.md
Creates the feature branch for planned work. Use at planning time before any code edits, or when the feature-branch hook blocks an edit on main.
development
Updated Apr 17, 2026
$ install --global
skillsauthnpx skillsauth add pkuppens/pkuppens plan-branch-strategyInstall 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 17, 2026, 7:58 AM9.6s1 file scanned
SKILL.md
- name:
- plan-branch-strategy
- description:
- Creates the feature branch for planned work. Use at planning time before any code edits, or when the feature-branch hook blocks an edit on main.
Plan Branch Strategy
When to use
- At the start of planning, before any file edits
- When the feature-branch hook returns
HOOK:FEATURE_BRANCH_REQUIRED
Branch naming
See CLAUDE.md § Git Workflow for the canonical convention. Common prefixes (gitflow-style):
| Prefix | Use when |
|--------|----------|
| feature/NNN-… | New feature (most common) |
| hotfix/NNN-… | Urgent production fix |
| chore/… | Tooling, config, docs |
| epic/NNN-… | Large effort spanning multiple issues |
Repo conventions may vary; check the project’s CLAUDE.md or contribution docs.
Instructions
- Confirm the issue number (from
gh issue listor conversation context). - Choose the prefix per repo convention.
- Create and switch:
git checkout -b <prefix>/<NNN>-<slug>. - Verify:
git branch --show-current.
Example
git checkout -b feature/42-plan-mode-checklist
git branch --show-current # → feature/42-plan-mode-checklist
Integration
- Runs before implementation-construction.
- Branch is later used by integration-commit → integration-pr.
- Invoked by plan in Phase 2.
Related Skills
pkuppens/sync-branch
testing
VerifiedTrustedCommunity
Syncs remote default branch locally (checkout, fetch --prune, pull) and returns to the previous branch when it still exists. Reports stashes and worktrees not yet handled. Use when the user asks to sync main, update default branch, fetch/pull origin, or run /sync-branch.
SKILL.mdUpdated Jun 6, 2026
pkuppens/azure-devops-work-items
tools
VerifiedTrustedCommunity
Creates, queries, updates, and links Azure Boards work items via az boards CLI. Use when filing ADO work items, running WIQL queries, or setting area path, iteration, tags, and assignee.
SKILL.mdUpdated May 29, 2026
pkuppens/azure-devops-repos
tools
VerifiedTrustedCommunity
Creates, reviews, and completes Azure Repos pull requests and branch policies via az repos CLI. Use when opening ADO PRs, setting required reviewers, or configuring build validation policies.
SKILL.mdUpdated May 29, 2026
pkuppens/azure-devops-pipelines
development
VerifiedTrustedCommunity
Guides Azure Pipelines YAML structure, build validation on PRs, and staged deployment with environments and approvals. Use when authoring azure-pipelines.yml or configuring CI/CD on Azure DevOps.
SKILL.mdUpdated May 29, 2026