git-workflow

Configures git branching strategies, PR templates, and changelog automation for team repositories.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/medispis/opencode-config --skill git-workflow-medispis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/medispis/opencode-config/tree/main/skills/git-workflow
Command: npx skills add https://github.com/medispis/opencode-config --skill git-workflow-medispis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often lack consistent git practices, leading to messy commit histories, unprotected branches, and manual changelog work. This Skill standardizes branching strategies, PR processes, and release automation across a repository. ## Core Features & Use Cases - Branching Strategy Setup: Detects the current workflow and configures GitHub Flow, Git Flow, or trunk-based development based on team needs. - PR Automation: Generates PR templates, commit message conventions (conventional commits), and GitHub Actions for lint, test, and typecheck on every PR. - Changelog & Release Automation: Generates changelogs from conventional commits grouped by type with links to commits and PRs. - Use Case: A team adopting GitHub Flow can use this Skill to generate a PR template, commitlint config, branch protection rules, and PR check workflows in one pass. ## Quick Start Set up a GitHub Flow workflow with a PR template, conventional commit enforcement, and automated PR checks for my repository.

Frequently Asked Questions about git-workflow

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

FAQPage Schema
How do I set up a git branching strategy for my team?

Choose GitHub Flow for most teams, Git Flow for scheduled releases, or trunk-based development for mature CI/CD pipelines. The Skill detects your current workflow first, then generates the matching branch protection and PR configuration.

How to enforce conventional commit messages in a repository?

Use a commitlint configuration that enforces the format type(scope): description with types like feat, fix, docs, refactor, test, and chore. Pair it with PR checks in CI so non-conforming commits are blocked before merge.

GitHub Flow vs Git Flow: which branching strategy should I use?

GitHub Flow keeps main always deployable with short feature branches and PRs, suiting most teams. Git Flow adds develop, release, and hotfix branches, which fits projects with scheduled release cycles but adds complexity.

Does this git workflow setup support GitLab and Bitbucket?

Yes, the Skill supports GitHub, GitLab, and Bitbucket. It detects the existing platform and workflow before generating configuration so it does not overwrite current setups.

How do I automate changelog generation from commits?

Generate changelogs from conventional commits by grouping entries by type such as features, fixes, and breaking changes, with links to the related commits and PRs. This requires consistent commit message formatting across the team.