How do I install the Github Ops skill?

Run npx skillmds@latest add yaomeng1749/github-ops 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 Ops safe to use?

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

Which AI agents work with Github Ops?

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 Ops free to use?

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

Who published Github Ops?

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

Github Ops by yaomeng1749 — Agent Skill

Name: Github Ops
Rating: 4.5 (4 reviews)
Author: Yaomeng1749

Github Ops

GitHub operations: commit, push, PR, fix CI, address review comments. Replaces Codex github:github, github:gh-address-comments, github:gh-fix-ci, github:yeet. Use when user says 'push', 'create PR', 'fix CI', 'address comments', 'yeet', or needs Git/GitHub workflow help.

Yaomeng1749 Updated Sep 22, 2026

File contents

GitHub Operations

Unified GitHub workflow skill for Claude Code. Covers the functionality of:

github:github — repo, PR, issue management
github:gh-address-comments — address PR review comments
github:gh-fix-ci — diagnose and fix CI failures
github:yeet — quick commit + push + draft PR

All operations use the gh CLI (GitHub CLI) and standard git commands.

Commands

/github-ops yeet

Quick ship: stage → commit → push → open draft PR.

git status to see changes
git diff --staged and git diff to understand changes
Stage relevant files (prefer explicit paths over git add -A)
Commit with a descriptive message
Push to remote with -u flag
gh pr create --draft with auto-generated title and body

/github-ops fix-ci

Diagnose and fix CI/GitHub Actions failures.

gh run list --limit 5 to find recent runs
gh run view <id> --log-failed to get failure logs
Analyze the failure (build error, test failure, lint issue, etc.)
Fix the root cause in code
Commit and push the fix
Verify with gh run watch if applicable

/github-ops address-comments

Address PR review comments.

gh pr view <number> to get PR details
gh api repos/{owner}/{repo}/pulls/{number}/comments to get review comments
For each comment:
- Read the referenced file and line
- Implement the requested change
- Stage the fix
Commit all fixes with a message referencing the review
Push to the PR branch

/github-ops pr [action]

PR management.

create — create PR with summary and test plan
view [number] — view PR details and status
merge [number] — merge PR (after checks pass)
list — list open PRs

/github-ops issue [action]

Issue management.

create — create issue from description
view [number] — view issue details
list — list open issues
close [number] — close issue with comment

Rules

Never force push without user confirmation
Never skip hooks (--no-verify) without user confirmation
Prefer specific file staging over git add -A
Always include Co-Authored-By in commits when Claude Code writes the code
Check git status before any destructive operation

---name: github-opsdescription: GitHub operations: commit, push, PR, fix CI, address review comments. Replaces Codex github:github, github:gh-address-comments, github:gh-fix-ci, github:yeet. Use when user says 'push', 'create PR', 'fix CI', 'address comments', 'yeet', or needs Git/GitHub workflow help.---# GitHub OperationsUnified GitHub workflow skill for Claude Code. Covers the functionality of:- `github:github` — repo, PR, issue management- `github:gh-address-comments` — address PR review comments- `github:gh-fix-ci` — diagnose and fix CI failures- `github:yeet` — quick commit + push + draft PRAll operations use the `gh` CLI (GitHub CLI) and standard `git` commands.## Commands### /github-ops yeetQuick ship: stage → commit → push → open draft PR.1. `git status` to see changes2. `git diff --staged` and `git diff` to understand changes3. Stage relevant files (prefer explicit paths over `git add -A`)4. Commit with a descriptive message5. Push to remote with `-u` flag6. `gh pr create --draft` with auto-generated title and body### /github-ops fix-ciDiagnose and fix CI/GitHub Actions failures.1. `gh run list --limit 5` to find recent runs2. `gh run view <id> --log-failed` to get failure logs3. Analyze the failure (build error, test failure, lint issue, etc.)4. Fix the root cause in code5. Commit and push the fix6. Verify with `gh run watch` if applicable### /github-ops address-commentsAddress PR review comments.1. `gh pr view <number>` to get PR details2. `gh api repos/{owner}/{repo}/pulls/{number}/comments` to get review comments3. For each comment: - Read the referenced file and line - Implement the requested change - Stage the fix4. Commit all fixes with a message referencing the review5. Push to the PR branch### /github-ops pr [action]PR management.- `create` — create PR with summary and test plan- `view [number]` — view PR details and status- `merge [number]` — merge PR (after checks pass)- `list` — list open PRs### /github-ops issue [action]Issue management.- `create` — create issue from description- `view [number]` — view issue details- `list` — list open issues- `close [number]` — close issue with comment## Rules- Never force push without user confirmation- Never skip hooks (--no-verify) without user confirmation- Prefer specific file staging over `git add -A`- Always include Co-Authored-By in commits when Claude Code writes the code- Check `git status` before any destructive operation

Frequently asked questions