Results for “git-friendly”

Create standardized, semantic git commits using the Conventional Commits specification by analyzing diffs to determine type, scope, and message.

Create Git branches following the Conventional Branch specification (feature/, bugfix/, hotfix/, release/, chore/). Validates branch names and automates checkout from the correct base branch.

Safely create, adopt, publish, or clean up an issue-backed non-primary Git branch without force-pushing or absorbing ambiguous work

Handles git and GitHub operations using the gh CLI, triggered by any github.com URL. Covers creating and reviewing PRs, watching CI checks, interactive rebasing, branch cleanup, submodule management, and repository archaeology.

Sets up an isolated Git worktree for feature development, preferring native tools and falling back to manual git worktrees when needed.

Creates standardized git commits using the Conventional Commits specification by analyzing the diff, staging files, and generating appropriate commit messages.

Structures git workflow practices for committing, branching, resolving conflicts, and organizing work across multiple parallel streams.

Decide whether Git submodules are the right boundary for external dependencies, then execute the appropriate workflow: add and pin, bootstrap recursively, sync to a recorded commit, advance a tracked branch, edit inside a submodule without detached-HEAD surprises, remove cleanly, or configure CI checkout constraints.

Fetch GitHub issues, select candidates, spawn background fix agents, open PRs, and optionally process PR review comments.

Use when automating GitHub issues, pull requests, reviews, CI checks, labels, releases, or engineering collaboration loops through the GitHub CLI.

Provides guidelines for writing conventional commit messages and pull request descriptions, including merge strategy and GitHub username verification.

Create, search, triage, and label GitHub issues using the gh CLI or REST API, with guidance on avoiding duplicates and managing the backlog.

Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping

Git workflows, branching strategies, and hooks.

Guides Git version control practices: branching strategies, commit conventions, merge vs rebase, conflict resolution, and pull request workflows for collaborative teams.

Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).

Transforms technical git commits into a clear, compact, user-friendly changelog. Use when preparing release notes, creating product update summaries, documenting changes for customers, or maintaining a public changelog page.

Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.

Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.