skills.rest
l3ocho
l3ochoCOMMUNITY
Explore all skills by this author →
GitHub

branch-security

Detect current branch, classify its type, and enforce branch-aware authorization.

Updated Jan 26, 2026
Search Tags:#git#workflow#devops#authorization#branch-detection#branch-classification#branch-security
One-click install
npx skills add https://github.com/l3ocho/mktpl-claude-datasaas --skill branch-security
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: branch-security
Source: https://github.com/l3ocho/mktpl-claude-datasaas/tree/main/plugins/projman/skills/branch-security
Command: npx skills add https://github.com/l3ocho/mktpl-claude-datasaas --skill branch-security

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill defines branch detection, classification, and branch-aware authorization rules to prevent unsafe actions based on branch context.

Core Features & Use Cases

  • Branch detection and classification for development, staging, and production workflows
  • Branch-aware stop messages and guided user prompts to enforce governance
  • Integration with planning, orchestration, and execution steps to guard code changes

Quick Start

Run the branch-security check in your repository to validate branch-detection, classification, and authorization behavior.

Frequently Asked Questions about branch-security

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce branch rules to prevent unsafe code changes in Git workflows?▼

To enforce branch rules, you can use branch detection and classification to apply branch-aware authorization, preventing unsafe changes on protected branches during sprint planning, execution, and deployment.

What is branch-aware authorization in DevOps and how does it work?▼

Branch-aware authorization detects the current Git branch, classifies its type as development, staging, or production, and enforces governance by applying explicit stop messages and guided prompts to ensure safe workflows.

How do I classify Git branches for staging and production environments?▼

You classify Git branches using defined naming conventions that identify them as development, staging, or production, allowing your workflow to apply the correct authorization rules and prevent unsafe changes on protected branches.

Can I block code changes on protected branches during sprint execution?▼

Yes, branch security integrates with planning, orchestration, and execution steps to guard code changes, applying branch-aware stop messages to block unsafe actions on protected branches during sprint execution.

Does branch security require external dependencies to run in my repository?▼

No, this branch security skill has no external dependencies or components, allowing you to run the branch detection and authorization check directly in your repository to validate classification behavior.

Why do my deployment workflows fail with stop messages on certain Git branches?▼

Deployment workflows fail with stop messages because branch classification identifies the current branch as protected, triggering explicit branch-aware stop messages to prevent unsafe changes during deployment.

Related Skills

Explore More Software Engineering Skills→
yanochka11yanochka11

create-branch

Create standardized git branches using repository naming conventions and change types.

Community
Intermediate
denniscalazansdenniscalazans
3

clean-branches

Remove local Git branches already integrated into the default branch.

Community
Intermediate
coco-decoco-de

Scrum Master

Break epics into user stories and sync sprint artifacts with ZenHub.

Official
Advanced
skaisserskaisser
4

bp-push

Push the current Git branch to the remote with branch guardrails.

Community
Advanced