How do I install the Github Workflow skill?

Run npx skillmds@latest add mabyko/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?

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

Github Workflow by mabyko — Agent Skill

Name: Github Workflow
Author: mabyko

Github Workflow

Use when working with GitHub workflows: pull requests, PR reviews, review threads, PR merges, auto-merge, GitHub Actions checks, CI annotations, branch protection, GitHub Releases, gh CLI commands, release publishing, or fork upstream-sync automation.

mabyko b22aa3c 6 files · 18.9 KB Updated Sep 17, 2026

File contents

GitHub Workflow

Use for GitHub-hosted collaboration and publishing. Use git-workflow for local staging, commits, rebases, conflicts, branch cleanup, Git tag safety, or history rewrites.

Rules

Read repository-specific GitHub guidance first: .github/, PR templates, release workflows, branch protection notes, CONTRIBUTING.md, and README.md.
Never claim GitHub status, checks, reviews, or release state unless you inspected them.
Do not merge, close, publish, mark latest, delete releases, or delete remote branches unless explicitly requested.
Treat green status as necessary but not sufficient: also check annotations, warnings, bot comments, and review state.
For local Git history decisions, follow git-workflow.

Reference Routing

Read only the references needed for the requested task.

Reference	Use For
`references/pull-requests.md`	Creating PRs, PR descriptions, review responses, merge readiness
`references/stacked-prs.md`	Stacked PR chains, sequential squash merges, base retargeting
`references/github-releases.md`	GitHub Releases, release publishing, latest flag, published release recovery
`references/upstream-sync.md`	Explicit requests to create or review fork upstream-sync GitHub Actions workflows

GitHub Action Safety Checklist

Before merging, enabling auto-merge, publishing a release, changing release latest, or dismissing review/check state:

Check worktree and branch state using git-workflow when local changes or branch history matter.
Inspect the exact PR, release, check run, or review thread targeted by the request.
Confirm required checks, review state, branch protection, and requested merge/release mode.
Act only on the target named by the user or verified from repository metadata.
Report the command, URL, or API result used as evidence.

Default Workflow

Read repository-specific GitHub guidance.
Check worktree and branch state using git-workflow when needed.
Inspect GitHub status, reviews, and templates relevant to the request.
Make or recommend GitHub changes only within the user's requested scope.
Report verification source, remaining blockers, and follow-up actions.

---name: github-workflowdescription: Use when working with GitHub workflows: pull requests, PR reviews, review threads, PR merges, auto-merge, GitHub Actions checks, CI annotations, branch protection, GitHub Releases, gh CLI commands, release publishing, or fork upstream-sync automation.---# GitHub WorkflowUse for GitHub-hosted collaboration and publishing. Use `git-workflow` for local staging, commits, rebases, conflicts, branch cleanup, Git tag safety, or history rewrites.## Rules1. Read repository-specific GitHub guidance first: `.github/`, PR templates, release workflows, branch protection notes, `CONTRIBUTING.md`, and `README.md`.2. Never claim GitHub status, checks, reviews, or release state unless you inspected them.3. Do not merge, close, publish, mark latest, delete releases, or delete remote branches unless explicitly requested.4. Treat green status as necessary but not sufficient: also check annotations, warnings, bot comments, and review state.5. For local Git history decisions, follow `git-workflow`.## Reference RoutingRead only the references needed for the requested task.| Reference | Use For || --- | --- || `references/pull-requests.md` | Creating PRs, PR descriptions, review responses, merge readiness || `references/stacked-prs.md` | Stacked PR chains, sequential squash merges, base retargeting || `references/github-releases.md` | GitHub Releases, release publishing, latest flag, published release recovery || `references/upstream-sync.md` | Explicit requests to create or review fork upstream-sync GitHub Actions workflows |## GitHub Action Safety ChecklistBefore merging, enabling auto-merge, publishing a release, changing release `latest`, or dismissing review/check state:- Check worktree and branch state using `git-workflow` when local changes or branch history matter.- Inspect the exact PR, release, check run, or review thread targeted by the request.- Confirm required checks, review state, branch protection, and requested merge/release mode.- Act only on the target named by the user or verified from repository metadata.- Report the command, URL, or API result used as evidence.## Default Workflow1. Read repository-specific GitHub guidance.2. Check worktree and branch state using `git-workflow` when needed.3. Inspect GitHub status, reviews, and templates relevant to the request.4. Make or recommend GitHub changes only within the user's requested scope.5. Report verification source, remaining blockers, and follow-up actions.

Frequently asked questions