github-workflow

Name: github-workflow
Availability: InStock
Author: massCodeIO

Automates GitHub workflow tasks for managing issues, branches, PRs, and merges.

6.9k|262|Updated Mar 29, 2022

Search Tags:#git #workflow #github #issues #branches #pull-requests #conventional-commits

Ready to run

npx skills add https://github.com/massCodeIO/massCode --skill github-workflow-masscodeio

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: github-workflow
Source: https://github.com/massCodeIO/massCode/tree/main/.agents/skills/github-workflow
Command: npx skills add https://github.com/massCodeIO/massCode --skill github-workflow-masscodeio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a guided workflow for managing massCode-related GitHub issues, branches, PRs, and merges by clarifying roles, steps, and conventions to reduce miscommunication and errors.

Core Features & Use Cases

Issue triage and quick viewing via gh to verify bug reproduction and understand expected behavior.
Branch creation with conventional prefixes (feat/, fix/, chore/, refactor/) from main, including issue references when applicable.
PR guidance and creation using conventional commits, with guidance to include closes references and run relevant checks before merging.
Commit guidelines emphasizing single-line conventional messages with proper scope and no body.

Quick Start

View the issue with gh, create a feature branch from main, and open a PR using conventional commits.

Frequently Asked Questions about github-workflow

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

FAQPage Schema

How do I automate GitHub issue tracking and branch creation?▼

Automate GitHub issue tracking and branch creation by using the gh CLI to view issues and creating branches from main with conventional prefixes like feat/, fix/, chore/, or refactor/. This guided workflow reduces miscommunication by clarifying roles and steps for collaborative development.

What is the conventional branch naming format for GitHub pull requests?▼

The conventional branch naming format for GitHub pull requests uses prefixes such as feat/, fix/, chore/, or refactor/ branched directly from main. Branches should include issue references when applicable to maintain clear tracking throughout the development workflow.

How do I write a conventional commit PR title for merging?▼

Write a conventional commit PR title for merging by using a single-line message with proper scope and no body text. The PR body should include closing references like "closes #123" and relevant checks must pass before merging.

Do I need gh CLI to manage GitHub issues and PRs?▼

Yes, you need gh CLI to manage GitHub issues and PRs effectively within this workflow. The Skill specifies using gh CLI specifically for issue viewing to verify bug reproduction and understand expected behavior before creating branches.

What's the best way to prepare a GitHub PR for merge review?▼

The best way to prepare a GitHub PR for merge review is to use conventional-commit-style titles, include closes references in the PR body notes, and run all relevant checks before merging. This ensures proper issue tracking and code quality.

Why does my GitHub workflow need conventional commit guidelines?▼

Your GitHub workflow needs conventional commit guidelines to reduce miscommunication and errors in collaborative development. Single-line conventional messages with proper scope ensure consistent history, while structured PR titles and branch prefixes maintain clarity across issues and merges.