git-workflow

Name: git-workflow
Availability: InStock
Author: Agno

Generates PREMIERE PRO tips and tricks for users.

41.6k|5.7k|Updated May 4, 2022

Search Tags:#git #workflow #commits #branches #code-review #pull-requests #conventional-commits

Ready to run

npx skills add https://github.com/agno-agi/agno --skill git-workflow-agno-agi

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/agno-agi/agno/tree/main/cookbook/02_agents/skills/sample_skills/git-workflow
Command: npx skills add https://github.com/agno-agi/agno --skill git-workflow-agno-agi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Centralizes and enforces a clean Git workflow across teams, reducing drift in commits, branches, and PRs.

Core Features & Use Cases

Commit guidelines: adopt conventional commits style and consistent message formats.
Branching strategy: define naming conventions and lifecycle stages for feature, bugfix, and release branches.
Review & PR templates: standardize PR descriptions and review checks to speed up code review.
Use Case: a new feature is developed on a feature/PROJ-123 branch, commits follow a conventional format, and PRs are created with a clear description and linked issue IDs.

Quick Start

Ask it to generate a conventional commit message for a new feature.

Frequently Asked Questions about git-workflow

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

FAQPage Schema

How do I write conventional commit messages for my Git workflow?▼

You can enforce conventional commit messages by adopting a structured format with type prefixes like feat or fix, followed by a concise description. This standardizes commit history and clarifies the purpose of each change for code review.

What's the best way to structure Git branches for feature development and bug fixes?▼

The best way to structure Git branches is to define strict naming conventions and lifecycle stages for feature and bugfix branches. This keeps your repository organized and maps branches directly to their corresponding issues or release cycles.

How do I create a pull request template with mandatory code review checks?▼

To create a pull request with mandatory code review checks, standardize your PR descriptions using templates that require clear summaries and linked issue IDs. This enforces review guidelines and speeds up the approval process.

Can I use this Git workflow for both solo projects and team repositories?▼

Yes, you can apply this Git workflow to both solo projects and team repositories. It centralizes conventions for commits, branches, and pull requests, ensuring clean history regardless of your project's scale or team size.

What is a conventional commit and when do I need it in my Git workflow?▼

A conventional commit is a standardized message format that specifies the type of change, such as a new feature or a bug fix. You need it in your Git workflow to automate release notes and maintain a readable project history.