skills.rest
I2olanD
I2olanDCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

git-workflow

Automate git branch creation, conventional commits, and pull requests.

Updated Dec 28, 2025
Search Tags:#git#workflow#branching#pull-request#commit-messages#spec-development
One-click install
npx skills add https://github.com/I2olanD/dotfiles --skill git-workflow-i2oland
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/I2olanD/dotfiles/tree/main/.config/opencode/skill/git-workflow
Command: npx skills add https://github.com/I2olanD/dotfiles --skill git-workflow-i2oland

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes and protects git operations across spec-driven development, reducing drift between spec, implement, and refactor work through consistent branching, commits, and PRs.

Core Features & Use Cases

  • Branch naming and lifecycle: Creates and guides branch names based on context (spec, feature, migrate, refactor) and ensures a clean lifecycle.
  • Commit messaging and PRs: Generates conventional commit messages and PR descriptions aligned with the spec context.
  • Safety and checks: Enforces repository checks, branch safety, and avoids destructive actions.

Quick Start

Install Git and GitHub CLI if needed. At the start of a spec or feature project, activate this skill to manage branches, commits, and PRs. When prompted, choose to create the appropriate branch (e.g., spec/001-name or feature/001-name) and follow prompts to commit changes and open a PR when ready.

Frequently Asked Questions about git-workflow

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

FAQPage Schema
How do I enforce a consistent git branching and commit workflow for spec-driven development?▼

To enforce a consistent git workflow for spec-driven development, you can automate branch creation, conventional commit messaging, and pull request generation while applying safety checks against destructive actions.

What is the best way to automate branch naming conventions for feature and spec tasks?▼

Automating branch naming conventions involves applying lifecycle rules to generate context-specific branches like spec/001-name or feature/001-name, ensuring a clean history and reducing drift between spec and implementation work.

How do I generate conventional commit messages aligned with my spec context?▼

Generating conventional commit messages aligned with spec context requires extracting task details to automatically create standardized commit descriptions that match the specific development phase.

Can I use GitHub CLI to automate pull request creation safely?▼

Yes, you can use GitHub CLI to automate pull request creation safely by enforcing repository checks and branch safety rules before opening PRs with spec-aligned descriptions.

Does this git workflow automation prevent destructive actions during branch lifecycle operations?▼

Yes, git workflow automation prevents destructive actions by enforcing repository checks and branch safety rules across verify status, branch creation, commits, and PR creation operations.

Do I need Git and GitHub CLI installed to manage spec-driven branch lifecycles?▼

Yes, you need Git and GitHub CLI installed to manage spec-driven branch lifecycles, as these tools provide the foundational repository operations required for branch creation and PR generation.

Related Skills

Explore More Software Engineering Skills→
QuintenpsQuintenps

git-workflow

Standardize version control operations with a three-branch model and git worktrees.

Community
Advanced
muskie9muskie9

merge-pr

Merge approved GitHub pull requests with branch cleanup and repository synchronization.

Community
Intermediate
ByronWilliamsCPAByronWilliamsCPA

Git Workflow Skill

Enforce branch validation, commit conventions, and PR preparation in Git workflows.

Official
Basic
vulikjulikvulikjulik

aif-commit

Generate conventional commit messages from staged git changes.

Community
Intermediate