Manage Git Branches and Worktrees
Complex Git workflows create inconsistent branches and risky merges. This skill guides branch strategy, naming, validation, and worktree operations across Claude, Codex, and Claude Code.
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "managing-branches" from https://skillstore.io/skills/c0ntr0lledcha0s-managing-branches.md and its manifest at https://skillstore.io/api/skills/c0ntr0lledcha0s-managing-branches/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Using "managing-branches". Start a feature branch for issue 42 about authentication.
Expected outcome:
The skill proposes a Gitflow feature branch from develop, links the issue, and lists commit and completion steps.
Using "managing-branches". Review our release branch process.
Expected outcome:
The skill identifies release branch targets, tag timing, cleanup rules, and checks needed before merging to production.
Using "managing-branches". Set up worktrees for a hotfix while feature work is active.
Expected outcome:
The skill recommends an isolated worktree, shows when to preserve current changes, and gives cleanup guidance after merge.
No malware, exfiltration, or prompt injection attempt was found. Most static findings are false positives from Markdown code fences, Git examples, configuration dictionaries, and transparent Git helper scripts. Residual risk is operational: some helper commands can push, tag, delete branches, or create worktrees in custom paths.
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
https://skillstore.io/skills/c0ntr0lledcha0s-managing-branches/audits/12?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report[](https://skillstore.io/skills/c0ntr0lledcha0s-managing-branches?utm_source=security_passport_badge)<a href="https://skillstore.io/skills/c0ntr0lledcha0s-managing-branches?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/c0ntr0lledcha0s-managing-branches/security.svg" alt="Skillstore security assessment" loading="lazy"></a><iframe src="https://skillstore.io/embed/skills/c0ntr0lledcha0s-managing-branches.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>C0ntr0lledCha0s. (2026). managing-branches security audit report (audit version 12) [Author version 1.0.0]. Skillstore. https://skillstore.io/skills/c0ntr0lledcha0s-managing-branches/audits/12@techreport{c0ntr0lledcha0s-c0ntr0lledcha0s-managing-branches-2026,
author = {C0ntr0lledCha0s},
title = {managing-branches security audit report (audit version 12)},
institution = {Skillstore},
year = {2026},
number = {12},
url = {https://skillstore.io/skills/c0ntr0lledcha0s-managing-branches/audits/12},
note = {Author version 1.0.0}
}cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "managing-branches security audit report (audit version 12)"
version: "1.0.0"
type: report
authors:
- name: "C0ntr0lledCha0s"
date-released: "2026-07-09"
url: "https://skillstore.io/skills/c0ntr0lledcha0s-managing-branches/audits/12"
identifiers:
- type: other
value: "skillstore:c0ntr0lledcha0s-managing-branches:audit:12"
description: "Skillstore immutable audit report identifier"
Each author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.
Why this variant is first
1gy-managing-branches
2026-08-21
c0ntr0lledcha0s-managing-branches
2026-08-21
Compare Gitflow, GitHub Flow, trunk-based, and environment flows for a repository before setting team rules.
Create feature, bugfix, hotfix, and release branches with consistent names and clear merge targets.
Validate branch names, merge direction, and cleanup steps before pull requests or releases.
Recommend a branch strategy for a small web team that deploys weekly. Explain the tradeoffs and first setup steps.
Create a branch naming convention for our repository. Include feature, bugfix, hotfix, release, docs, and refactor branches.
Check whether my current branch follows our Gitflow rules. Identify the target branch, merge path, and cleanup steps.
Design a worktree workflow for parallel hotfix and feature work. Include safe cleanup, branch deletion rules, and review checkpoints.
Author
C0ntr0lledCha0sLicense
MIT
Author version
v1.0.0
Skillstore revision
r1
Ref
3e4b6c31a74a3bd1a291c98cf585d720cb9fbc88
Maintenance freshness
7/18/2026
Usage
11 downloads · 218 views
File structure
Analyze Test Suite Quality
Coverage percentages alone cannot show whether tests are reliable, focused, or effective. This skill assesses quality dimensions and produces prioritized, evidence-based improvements.
Analyze Patterns Across Your Codebase
Large codebases hide repeated structures and inconsistent decisions. This skill maps design patterns, architecture, conventions, duplication, and anti-patterns with evidence and recommendations.
Build Reliable Jest Tests
Jest projects often fail because tests, mocks, asynchronous behavior, and configuration are inconsistent. This skill provides focused patterns for dependable JavaScript, TypeScript, React, and Node.js testing.
Build Reliable Playwright Tests
Playwright test suites can become flaky, slow, and difficult to maintain. This skill provides practical patterns for locators, fixtures, page objects, debugging, mocking, and configuration.
Organize GitHub Issues With Labels
Large repositories can lose track of issue priority, scope, and release status. This skill designs label taxonomies, applies labels in bulk, and manages milestones with GitHub CLI workflows.
Build Claude Code Agents
Creating reliable AI agents requires clear schemas, safe tools, and repeatable review steps. This skill guides agent design, validation, migration, and maintenance for Claude Code workflows.
Build Release Readiness Packets
by yaojingang
Release teams often have scattered notes, unclear rollback criteria, and missing communication plans. This skill turns those inputs into a structured release packet with readiness gates and go/no-go guidance.
Standardize Your Git Workflow
by Atman36
Inconsistent commits and branches make collaboration and releases harder to manage. This skill applies Conventional Commits, GitFlow, review practices, and pre-commit checks.
Build Production ML Pipelines
by wshobson
ML teams need repeatable pipelines that connect data preparation, training, validation, deployment, and monitoring. This skill guides Claude, Codex, and Claude Code through practical MLOps workflow design.
Master Advanced Git Workflows
by AutumnsGrove
Complex Git maintenance can make history changes and conflict resolution difficult. This skill provides structured guidance, recovery steps, and an optional local helper for common advanced workflows.
Create Slash Commands for AI Workflows
by DNYoussef
Repeated AI workflows are slow when users rely on long natural language prompts. This skill helps define concise slash commands with routing, validation, chaining, and help text.
Create Focused AI Micro-Skills
by DNYoussef
Reusable AI workflows often grow too broad and hard to test. This skill helps define focused skills with specialist prompts, contracts, and validation plans.