skills.rest
Shakudo-io
Shakudo-ioOFFICIAL
Explore all skills by this author →
WebsiteGitHub

git-workflow

Enforce Git branch, commit, and pull request conventions for business-automation projects.

Updated Feb 14, 2026
Search Tags:#git#workflow#branching#conventions#pull-request#commit-message
One-click install
npx skills add https://github.com/Shakudo-io/opencode-skills --skill git-workflow-shakudo-io
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/Shakudo-io/opencode-skills/tree/main/git-workflow
Command: npx skills add https://github.com/Shakudo-io/opencode-skills --skill git-workflow-shakudo-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The correct Git workflow ensures consistent branching, commits, and PR conventions for business-automation projects.

Core Features & Use Cases

  • Branch naming convention: NNN-feature-name
  • Commit Message Format: [subfolder] description, use present tense and be descriptive
  • Standard workflow: create branches, commit changes, push, and open PRs following the guidelines
  • Use case: when making code changes, creating branches, or preparing commits

Quick Start

Create a new branch using the NNN-feature-name pattern, commit changes with the described format, and open a PR following the conventions.

Frequently Asked Questions about git-workflow

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

FAQPage Schema
How do I standardize Git workflows for business automation projects?▼

Standardize Git workflows by enforcing the NNN-feature-name branch pattern, present-tense commit messages with subfolder prefixes, and structured PR conventions to ensure traceability and reviews across team repositories.

What is the best way to format commit messages for traceability?▼

The best way to format commit messages for traceability is using a subfolder prefix followed by a descriptive, present-tense statement, ensuring changes are easily tracked across project directories.

How do I name branches to match repository conventions?▼

Name branches using the NNN-feature-name pattern to match repository conventions, applying numerical identifiers to feature descriptions for consistent tracking and standardized pull request preparation.

Does this Git workflow support automated pull request preparation?▼

Yes, this Git workflow supports automated pull request preparation by enforcing PR conventions alongside branch creation and commit standardization to ensure consistent reviews and traceability.

When do I need to enforce strict Git branching and commit conventions?▼

You need to enforce strict Git branching and commit conventions when making code changes, creating branches, or preparing commits for business-automation projects to maintain consistent traceability and reviews.

Related Skills

Explore More Software Engineering Skills→
allanninalallanninal
1

git-automation

Automate Git operations including commit messages, branch management, hooks, and repository maintenance.

Community
Advanced
p-o-ke-naep-o-ke-nae

github-flow

Guide GitHub Flow branching, commits, testing, pull requests, and squash merges.

Community
Intermediate
AnveioAnveio
1

task-pull-request

Automate GitHub pull request creation, reviews, feedback, and merges via gh CLI.

Community
Intermediate
mpazarynampazaryna
1

push

Stage, commit, and push Git changes with conventional commit messages.

Community
Intermediate