branch-and-pr

Estrelas12

Forks2

Atualizado17 de janeiro de 2026 às 23:36

Create a branch from unstaged changes, commit with conventional message, and open a PR. Use when user wants to quickly ship current work.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Fonte

YousefHadder

YousefHadder/dotfiles

Abrir repositório GitHub Ver repositórios do creator

Download

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

name	branch-and-pr
description	Create a branch from unstaged changes, commit with conventional message, and open a PR. Use when user wants to quickly ship current work.

Branch and PR

Create a new branch, commit current changes, and open a pull request in one workflow.

Workflow

Analyze changes: Run git status and git diff to understand what changed
Generate branch name: Format {username}/{type}-{short-description}
- Get username from git config user.name (lowercase, no spaces)
- Type: feat, fix, refactor, docs, test, chore, perf, style
- Description: 2-4 words, kebab-case, derived from changes
Create branch: git checkout -b {branch-name}
Stage and commit:
- Stage all changes: git add -A
- Commit with conventional message: {type}: {description} (max 72 chars)
Pause for confirmation: Show the user what will be pushed
On confirmation: Push and create PR via gh pr create

Commit Message Style

Conventional format: type: lowercase description
No period at end
Imperative mood ("add" not "adds" or "added")
Max 72 characters
Examples:
- fix: handle null user in auth middleware
- feat: add dark mode toggle to settings
- refactor: extract validation logic to helper

PR Description Style

Write like a human developer, not an AI:

Title: Same as commit message or slightly expanded

Body structure:

Brief 1-2 sentence summary of what this does.

- Bullet points for specific changes if needed
- Keep it scannable

Tested by [how you verified it works]

Avoid:

"This PR introduces..." / "This commit adds..."
Overly formal language
Excessive bullet points
Explaining obvious things
Words like "comprehensive", "robust", "enhance"

Good examples:

"Fixes the crash when user logs out during sync"
"Adds retry logic for flaky API calls - was causing random failures in prod"
"Cleans up the auth module, no behavior changes"

Confirmation Prompt

Before pushing, show:

Branch: {branch-name}
Commit: {commit-message}

Changes to be pushed:
{file list}

Ready to push and create PR? (y/n)

Wait for explicit user confirmation before proceeding.

Mais deste repositório

mesmo repositório

onboard-repo

YousefHadder/dotfiles

This skill should be used when the user asks to "onboard", "analyze this repo", "understand this codebase", "familiarize yourself", "what is this project", or needs to deeply understand a codebase's architecture, patterns, and conventions before starting work.

2026-04-0712

aw-planner

YousefHadder/dotfiles

Analyze the current repo deeply and suggest agentic workflows tailored to its architecture, patterns, and pain points. Use when user calls /aw-planner.

2026-03-0812

read-issue

YousefHadder/dotfiles

Read a GitHub issue with all comments and linked content to add as working context. Use when the user provides a GitHub issue URL or reference.

2026-02-1312

manual-testing-guide

YousefHadder/dotfiles

Generate a comprehensive manual testing guide for completed work, with note sections for user feedback that the agent reviews afterward. Use when the user wants to manually test changes before shipping.

2026-02-1112

review-pr-comments

YousefHadder/dotfiles

Review PR comments, validate which are actionable and correct, and propose fixes for valid ones. Use when user wants to address feedback on a pull request.

2026-01-2712

zendesk-markdown

YousefHadder/dotfiles

Convert Markdown text to Zendesk-compatible HTML. Use when user needs to format content for Zendesk tickets, macros, triggers, or automations.

2026-01-2312

Branch and PR

Create a new branch, commit current changes, and open a pull request in one workflow.

Workflow

Analyze changes: Run git status and git diff to understand what changed

Generate branch name: Format {username}/{type}-{short-description}

Get username from git config user.name (lowercase, no spaces)
Type: feat, fix, refactor, docs, test, chore, perf, style
Description: 2-4 words, kebab-case, derived from changes

Create branch: git checkout -b {branch-name}

Stage and commit:

Stage all changes: git add -A
Commit with conventional message: {type}: {description} (max 72 chars)

Pause for confirmation: Show the user what will be pushed

On confirmation: Push and create PR via gh pr create

Commit Message Style

Conventional format: type: lowercase description

No period at end

Imperative mood ("add" not "adds" or "added")

Max 72 characters

Examples:

fix: handle null user in auth middleware
feat: add dark mode toggle to settings
refactor: extract validation logic to helper

PR Description Style

Write like a human developer, not an AI:

Title: Same as commit message or slightly expanded

Body structure:

Brief 1-2 sentence summary of what this does.

- Bullet points for specific changes if needed
- Keep it scannable

Tested by [how you verified it works]

Avoid:

"This PR introduces..." / "This commit adds..."

Overly formal language

Excessive bullet points

Explaining obvious things

Words like "comprehensive", "robust", "enhance"

Good examples:

"Fixes the crash when user logs out during sync"

"Adds retry logic for flaky API calls - was causing random failures in prod"

"Cleans up the auth module, no behavior changes"

Confirmation Prompt

Before pushing, show:

Branch: {branch-name} Commit: {commit-message} Changes to be pushed: {file list} Ready to push and create PR? (y/n)

Wait for explicit user confirmation before proceeding.