How do I install the Github Workflow skill?

Run npx skillmds@latest add huynhsontung/github-workflow in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Github Workflow safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Github Workflow?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Github Workflow free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Github Workflow?

huynhsontung (@huynhsontung) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Github Workflow by huynhsontung — Agent Skill

Name: Github Workflow
Author: huynhsontung

File contents

GitHub CLI & Git Workflow Runbook

Follow these structured procedures and guidelines when working with Git branches, commits, pull requests, and GitHub CLI (gh) commands.

1. GitHub CLI (`gh`) Guidelines for Windows

[!IMPORTANT] Always use --body-file (or -F) when passing markdown bodies to gh CLI commands on Windows. Never use inline strings (--body or -b) for multiline markdown, PR descriptions, issue bodies, or release notes. PowerShell and Windows CMD shell quoting frequently cause broken newlines, mangled quotes, and unwanted character escapes.

Creating a Pull Request with `gh pr create`

Write the PR description to a file (e.g., in a temporary or scratch directory):

# Example: write PR body to a temp markdown file
@'
## Context & Motivation
Brief description of the problem, background, and why this change was made.

## Key Changes & Impact
- Key change 1
- Key change 2

## Testing & Verification
- Ran automated tests via `dotnet run`
- Verified build with Visual Studio 2026 MSBuild
'@ | Set-Content -Path ./pr_body.md -Encoding utf8

Execute gh pr create using --body-file:

gh pr create --title "feat: descriptive title" --body-file ./pr_body.md --base main

Clean up the temporary file:

Remove-Item -Path ./pr_body.md -ErrorAction SilentlyContinue

Creating or Editing Issues with `gh`

Similarly, always write issue bodies to a file and supply --body-file:

gh issue create --title "bug: descriptive title" --body-file ./issue_body.md

2. Commit Message & PR Title Conventions

Use the Conventional Commits standard.
Format: <type>(<optional-scope>): <short summary>
- feat: A new feature
- fix: A bug fix
- docs: Documentation changes only
- refactor: Code changes that neither fix a bug nor add a feature
- perf: Performance improvements
- test: Adding or correcting tests
- chore: Maintenance tasks, dependency updates, build tooling
PR titles must follow conventional commit naming.
PR descriptions must include Context, Motivation, and Impact, referencing any related issues (Fixes #123, Resolves #456).

3. Branching & Push Workflow

Ensure changes are committed with conventional messages.
Push branch to remote:
```
git push -u origin <branch-name>
```
Open pull request using gh pr create --body-file <path>.

---name: github-workflowdescription: Procedures and guidelines for Git operations and GitHub CLI (`gh`) commands, including branch management, commit messages, and creating pull requests or issues.---# GitHub CLI & Git Workflow RunbookFollow these structured procedures and guidelines when working with Git branches, commits, pull requests, and GitHub CLI (`gh`) commands.---## 1. GitHub CLI (`gh`) Guidelines for Windows> [!IMPORTANT]> **Always use `--body-file` (or `-F`) when passing markdown bodies to `gh` CLI commands on Windows.**> Never use inline strings (`--body` or `-b`) for multiline markdown, PR descriptions, issue bodies, or release notes. PowerShell and Windows CMD shell quoting frequently cause broken newlines, mangled quotes, and unwanted character escapes.### Creating a Pull Request with `gh pr create`1. **Write the PR description to a file** (e.g., in a temporary or scratch directory): ```pwsh # Example: write PR body to a temp markdown file @' ## Context & Motivation Brief description of the problem, background, and why this change was made. ## Key Changes & Impact - Key change 1 - Key change 2 ## Testing & Verification - Ran automated tests via `dotnet run` - Verified build with Visual Studio 2026 MSBuild '@ | Set-Content -Path ./pr_body.md -Encoding utf8 ```2. **Execute `gh pr create` using `--body-file`**: ```pwsh gh pr create --title "feat: descriptive title" --body-file ./pr_body.md --base main ```3. **Clean up the temporary file**: ```pwsh Remove-Item -Path ./pr_body.md -ErrorAction SilentlyContinue ```### Creating or Editing Issues with `gh`Similarly, always write issue bodies to a file and supply `--body-file`:```pwshgh issue create --title "bug: descriptive title" --body-file ./issue_body.md```---## 2. Commit Message & PR Title Conventions- Use the [Conventional Commits](https://www.conventionalcommits.org/) standard.- Format: `<type>(<optional-scope>): <short summary>` - `feat`: A new feature - `fix`: A bug fix - `docs`: Documentation changes only - `refactor`: Code changes that neither fix a bug nor add a feature - `perf`: Performance improvements - `test`: Adding or correcting tests - `chore`: Maintenance tasks, dependency updates, build tooling- PR titles must follow conventional commit naming.- PR descriptions must include **Context**, **Motivation**, and **Impact**, referencing any related issues (`Fixes #123`, `Resolves #456`).---## 3. Branching & Push Workflow1. Ensure changes are committed with conventional messages.2. Push branch to remote: ```pwsh git push -u origin <branch-name> ```3. Open pull request using `gh pr create --body-file <path>`.

Frequently asked questions

Github Workflow