📦

branch

Name: branch
Author: Clionegohan

Content revision r1 Medium Risk ⚙️ External commands

Create Git Workflow Branches

Manual branch naming can slow specification and implementation workflows. This skill guides Claude, Codex, or Claude Code to create consistent spec and impl branches.

Supports: Claude Codex Code(CC)

📊 70 Adequate

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "branch" from https://skillstore.io/skills/clionegohan-branch.md and its manifest at https://skillstore.io/api/skills/clionegohan-branch/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.

Markdown detail GET /skills/clionegohan-branch.md Signed manifest GET /api/skills/clionegohan-branch/manifest Signed lockfile GET /api/skills/clionegohan-branch/lockfile

Test it

Using "branch". Create a spec branch for action 001-01-01 named user auth.

Expected outcome:

Proposed branch: spec/001-01-01-user-auth
Base branch: main
Status: waiting for confirmation before creating the branch

Using "branch". Start implementation for action 002-03-04 with description audit-log.

Expected outcome:

Proposed branch: impl/002-03-04-audit-log
Uncommitted changes detected
Options: stash changes, commit changes, or cancel branch creation

Security Audit

Medium Risk

v8 • 7/5/2026 Open versioned report

Most static findings are false positives caused by Markdown backticks, code fences, and inline examples. The remaining concern is semantic: the documented Git checkout command uses a branch-name placeholder that should be validated before any shell execution.

Files scanned

147

Lines analyzed

Review items

False positives ignored

Confirmed security concerns (1)

Medium

SKILL.md:62-64 SKILL.md:100-108

Unvalidated Branch Name in Git Command

The skill accepts action-id and description values, then documents git checkout with a branch-name placeholder. If an agent interpolates unsafe text into a shell command, branch names could be misinterpreted as shell syntax or Git options.

The placeholder and user-controlled inputs are visible, but no executable implementation is included. Risk depends on how Claude, Codex, or Claude Code runs the documented command.

Audited by: codex View Audit History →

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.

Open versioned report

Copy report link

https://skillstore.io/skills/clionegohan-branch/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/clionegohan-branch/security.svg)](https://skillstore.io/skills/clionegohan-branch?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/clionegohan-branch?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/clionegohan-branch/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/clionegohan-branch.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

Clionegohan. (2026). branch security audit report (audit version 8) [Author version unspecified]. Skillstore. https://skillstore.io/skills/clionegohan-branch/audits/8

BibTeX citation

@techreport{clionegohan-clionegohan-branch-2026,
  author = {Clionegohan},
  title = {branch security audit report (audit version 8)},
  institution = {Skillstore},
  year = {2026},
  number = {8},
  url = {https://skillstore.io/skills/clionegohan-branch/audits/8},
  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: "branch security audit report (audit version 8)"
version: "unspecified"
type: report
authors:
  - name: "Clionegohan"
date-released: "2026-07-05"
url: "https://skillstore.io/skills/clionegohan-branch/audits/8"
identifiers:
  - type: other
    value: "skillstore:clionegohan-branch:audit:8"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Start a specification branch

Create a spec branch before drafting requirements or design notes.

Open an implementation branch

Create an impl branch before coding an approved action item.

Standardize branch naming

Keep team branches aligned with action IDs and short descriptions.

Try These Prompts

Create a spec branch

Use the branch skill to create a spec branch for action 001-01-01 with description user-auth. Ask before running Git commands.

Create an implementation branch

Create an impl branch for action 001-01-01 using the current repository. Confirm the base branch and branch name first.

Handle an existing branch

Prepare a spec branch for action 002-02-03. If it already exists, show safe options before switching or creating another branch.

Run a guarded branch workflow

Create an impl branch for action 003-04-05 payment-retry. Validate the branch name, check local changes, and ask before each Git action.

Best Practices

Confirm the base branch and branch name before creating anything.
Use short descriptions with letters, numbers, and hyphens.
Resolve uncommitted changes before switching branches.

Avoid

Creating branches without user confirmation.
Using long descriptions or unsupported characters in branch names.
Discarding local changes just to make branch creation easier.

Frequently Asked Questions

What branch types does this skill support?

It supports spec branches for planning and impl branches for implementation work.

Does it create remote branches?

No. It describes local branch creation and does not publish branches to a remote repository.

Can I use it with Claude Code?

Yes. The workflow is written for Claude, Codex, and Claude Code environments with Git access.

Does it require user confirmation?

Yes. The skill instructs the assistant to ask before creating a branch.

What happens if the branch already exists?

The skill asks the user to switch branches, choose another name, or delete the existing branch.

What should I check before using it?

Check your current branch, uncommitted changes, and the generated branch name.

Developer Details

Author

Clionegohan

License

MIT

Skillstore revision

Version notice

The author did not declare a version.

Repository

https://github.com/Clionegohan/YoRuH-Resonance-Archive-C4-Sync-/tree/main/atdd-sdd/.claude/skills/branch

Ref

02f077c174c5335e2f5d02ca15e77b70d9543e58

Maintenance freshness

7/22/2026

Usage

7 downloads · 190 views

File structure

📄 SKILL.md