git-workflow

Branch from issues, commit with conventional format, and open PRs per project conventions.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/rodacato/kwik-e-dev --skill git-workflow-rodacato
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/rodacato/kwik-e-dev/tree/main/plugins/lifecycle/skills/git-workflow
Command: npx skills add https://github.com/rodacato/kwik-e-dev --skill git-workflow-rodacato

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Executes project-wide git hygiene from one well-defined entry point: branch → commit → PR. Reads project conventions FIRST (CLAUDE.md, AGENTS.md, CONTRIBUTING.md) so it honors per-project overrides instead of imposing a default. Refuses destructive operations without explicit human confirmation.

Core Features & Use Cases

  • Branch from the issue using project-specific naming conventions (e.g., issue-<N>-<short-description>).
  • Commit with the conventional format and a focused scope.
  • Open a PR that references the issue and follows the project PR template and required body sections.
  • Read CLAUDE.md / AGENTS.md / CONTRIBUTING.md to honor overrides; refuse destructive actions without explicit confirmation.
  • Enforce safe workflows to prevent pushing to main and bypassing hooks.

Quick Start

Branch from the issue, commit using the project's conventional format, and open a PR that closes the issue according to CLAUDE.md, AGENTS.md, and CONTRIBUTING.md conventions.

Frequently Asked Questions about git-workflow

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

FAQPage Schema
How do I automate a git workflow from branching to opening a pull request?

Automating a git workflow from branching to pull request involves reading project conventions in CLAUDE.md or CONTRIBUTING.md, creating a conventionally named branch, committing with conventional commit formats, and opening a PR that closes the linked issue.

How do I enforce conventional commits and project-specific PR templates?

Enforcing conventional commits and PR templates requires reading project override files like AGENTS.md and CONTRIBUTING.md before applying default formatting, ensuring commit messages follow the project scope and PR bodies include required sections.

Can I use CLAUDE.md and AGENTS.md to override default git branching conventions?

Yes, you can use CLAUDE.md and AGENTS.md to override default git branching conventions by documenting project-specific naming patterns and PR rules, which are read and honored before any default branch or commit formatting is applied.

What is the best way to prevent pushing directly to main or bypassing git hooks?

Preventing pushes to main and bypassing git hooks is achieved by enforcing safe git workflows that block destructive actions without explicit human confirmation, ensuring branch protection and proper issue-to-branch routing.

Why does my pull request not reference the original issue automatically?

A pull request may not reference the original issue if the git workflow did not branch from the issue context or apply the closing keyword syntax in the PR body as specified in project convention files.

Do I need an existing branch to start formatting commits with conventional messages?

No, you do not need an existing branch; the git workflow applies when starting work on an issue with no existing branch, creating one with project-specific naming conventions before formatting commits with conventional messages.