skills.rest
crsiebler
crsieblerCOMMUNITY
Explore all skills by this author →
Website𝕏@CorySieblerGitHub

git-manager

Manage Git branches, commits, and pull requests with Git Flow conventions.

1|Updated Dec 13, 2025
Search Tags:#git#pull request#branch management#git flow#commit practices
One-click install
npx skills add https://github.com/crsiebler/pogo-team-generator --skill git-manager-crsiebler
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-manager
Source: https://github.com/crsiebler/pogo-team-generator/tree/main/.opencode/skills/git-manager
Command: npx skills add https://github.com/crsiebler/pogo-team-generator --skill git-manager-crsiebler

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures a consistent and efficient Git workflow by managing branches, commits, and pull requests, reducing errors and improving collaboration.

Core Features & Use Cases

  • Branch Management: Create and manage feature branches with proper naming conventions.
  • Commit Practices: Encourage atomic, conventional commits for better code history.
  • Pull Request Creation: Automate the push and creation of pull requests for code review.
  • Use Case: When starting a new feature, this Skill guides you through creating a branch, making commits, and opening a pull request, ensuring a smooth and consistent workflow.

Quick Start

Use the git-manager skill to create a new feature branch: git checkout -b feat/new-feature.

Frequently Asked Questions about git-manager

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

FAQPage Schema
How do I create a feature branch following Git Flow conventions?▼

To create a feature branch following Git Flow conventions, use a naming pattern like `feat/new-feature` to branch off your main codebase. This ensures organized branch management and prepares your work for structured code review.

What is the best way to enforce consistent commit practices in Git?▼

The best way to enforce consistent commit practices is to use atomic, conventional commits for your code history. This approach separates changes into logical units, improving code traceability and collaboration across your development team.

How do I automate pull request creation from the command line?▼

You automate pull request creation by integrating your commit workflow with push commands to open code reviews directly. This streamlines the transition from local branch management to remote collaboration without manual web interface interaction.

Do I need to know Git Flow to use this branch management workflow?▼

Yes, you need basic Git commands and knowledge of the Git Flow branching model to use this workflow. Understanding Git Flow is required to properly adhere to the structured branching and pull request creation process.

Why use conventional commits for code collaboration?▼

You use conventional commits for code collaboration to ensure an efficient, error-free workflow across your team. Standardized commit messages maintain a clear project history and make tracking changes through pull requests much easier.

Related Skills

Explore More Software Engineering Skills→
JuanMS20JuanMS20

github-auth

Configure GitHub authentication for Hermes Agent using git, gh CLI, or SSH credentials.

Community
Intermediate
mdmagnuson-creatormdmagnuson-creator

merge-conflicts

Merge target branches into source branches and resolve pull request conflicts.

Community
Advanced
automatedigitalautomatedigital
1

requesting-code-review

Scan git code changes for security vulnerabilities and test regressions before commit.

Official
Advanced
ginkidaginkida
20

git-expert

Automate Git branching, rebasing, and conflict resolution workflows.

Community
Advanced