ciberbal-ai-branch-pr

Creates branches and pull requests on GitHub following issue-first enforcement and Conventional Commits rules.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/Balthael/ciberbal-ai --skill ciberbal-ai-branch-pr-balthael
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ciberbal-ai-branch-pr
Source: https://github.com/Balthael/ciberbal-ai/tree/main/skills/branch-pr
Command: npx skills add https://github.com/Balthael/ciberbal-ai --skill ciberbal-ai-branch-pr-balthael

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Contributors to the ciberbal-ai repository often get pull requests automatically rejected by CI because they miss required issue links, type labels, branch naming rules, or commit message formats. This Skill encodes the entire contribution workflow so every PR passes the 5 automated checks on the first attempt. ## Core Features & Use Cases - Issue-First Enforcement: Verifies the linked issue has status:approved before any work begins, since PRs without an approved linked issue are automatically rejected. - Branch Naming & Conventional Commits: Enforces the type/description branch pattern and Conventional Commits format, including breaking-change notation with !. - PR Template & Label Compliance: Generates the full PR body from the required template and ensures exactly one type:* label is applied. - Use Case: You fixed a bug in Claude Code detection on Linux. The Skill walks you through confirming issue #42 is approved, creating fix/claude-detection-linux, running go test ./... and the Docker E2E suite, and opening a compliant PR with gh pr create. ## Quick Start Ask the agent to create a branch and open a pull request on Balthael/ciberbal-ai for your approved issue, following the repository's naming, commit, and labeling rules.

Frequently Asked Questions about ciberbal-ai-branch-pr

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

FAQPage Schema
How do I create a pull request for the ciberbal-ai repository?

First confirm the linked issue has the status:approved label using gh issue view, then create a branch matching the type/description pattern, commit with Conventional Commits, and open the PR with gh pr create using the required body template and exactly one type:* label.

Why was my pull request automatically rejected by CI?

PRs are rejected when the body lacks a Closes/Fixes/Resolves #N reference, the linked issue is missing status:approved, or zero or multiple type:* labels are applied. Failing unit tests or Docker E2E tests also block merging.

What branch naming convention does ciberbal-ai use?

Branches must match ^(feat|fix|chore|docs|style|refactor|perf|test|build|ci|revert)/[a-z0-9._-]+$, all lowercase with hyphens, dots, or underscores as separators, such as fix/duplicate-observation-insert.

What commit message format is required for contributions?

Commits must follow Conventional Commits: type(optional-scope): description, using types like feat, fix, docs, refactor, chore, style, perf, test, build, ci, or revert. Breaking changes add ! after the type, and Co-Authored-By trailers are forbidden.

How do I run the tests required before opening a PR?

Run unit tests with go test ./... from the repository root, and run E2E tests with cd e2e && ./docker-test.sh, which requires Docker to be running. Both suites must pass before the PR can merge.