managing-branches
Manage Git Branches Safely
Branch state can be unclear during active repository work. This skill guides Claude, Codex, and Claude Code through focused Git checks and branch creation steps.
Install with my Agent
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/1gy-managing-branches.md and its manifest at https://skillstore.io/api/skills/1gy-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.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "managing-branches". Check whether this repository is ready for new work.
Expected outcome:
Current branch is feature/login. There are two modified files. Remote tracking is current. The branch is three commits ahead of main.
Using "managing-branches". Create a branch for the billing update from main.
Expected outcome:
Created the requested branch from origin/main. No local changes were present. Remote branch information was fetched before creation.
Using "managing-branches". Why did my branch operation fail?
Expected outcome:
The target branch already exists and local changes are present. Choose the existing branch, provide a new name, or commit the changes first.
Security Audit
SafeStatic findings are false positives caused by Markdown code fences, inline command formatting, and harmless stderr redirection. No prompt injection, data exfiltration intent, or hidden unsafe behavior was found in SKILL.md.
Risk Factors
⚙️ External commands (7)
📁 Filesystem access (1)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/1gy-managing-branches/audits/6?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/1gy-managing-branches?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/1gy-managing-branches?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/1gy-managing-branches/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/1gy-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>Academic citations (APA · BibTeX · CFF)
APA citation
1gy. (2026). managing-branches security audit report (audit version 6) [Author version unspecified]. Skillstore. https://skillstore.io/skills/1gy-managing-branches/audits/6BibTeX citation
@techreport{1gy-1gy-managing-branches-2026,
author = {1gy},
title = {managing-branches security audit report (audit version 6)},
institution = {Skillstore},
year = {2026},
number = {6},
url = {https://skillstore.io/skills/1gy-managing-branches/audits/6},
note = {Author version unspecified}
}CITATION.cff
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 6)"
version: "unspecified"
type: report
authors:
- name: "1gy"
date-released: "2026-07-04"
url: "https://skillstore.io/skills/1gy-managing-branches/audits/6"
identifiers:
- type: other
value: "skillstore:1gy-managing-branches:audit:6"
description: "Skillstore immutable audit report identifier"
Compare variants
2 installable variantsEach 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
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Review Branch State Before Coding
Check the active branch, local changes, remote sync state, and commits ahead of main before starting work.
Create Feature Branches Consistently
Fetch a base branch and create a new local branch from the matching remote branch.
Diagnose Branch Workflow Errors
Identify existing branches, uncommitted changes, remote fetch issues, permission errors, and conflict status.
Try These Prompts
Use the managing-branches skill to check the current branch, local changes, remote sync status, and commits ahead of main.
Use the managing-branches skill to create a new feature branch from origin/main. Report any uncommitted changes before creating it.
Use the managing-branches skill to investigate why branch creation failed. Check existing branches, remote sync, permissions, and local changes.
Use the managing-branches skill to produce a branch readiness report with current branch, changes, ahead count, remote state, and required user decisions.
Best Practices
- Run the branch check before creating or switching branches.
- Confirm the intended base branch before creating new work branches.
- Resolve or save local changes before branch operations that change state.
Avoid
- Creating branches without checking for uncommitted local work.
- Assuming the main branch name without checking project guidance.
- Continuing through complex conflicts without asking the user.