Github Ops

Name: Github Ops
Author: majiayu000

ASecurity

GitHub operations wrapper. Helps manage PRs, Issues, and Reviews efficiently via CLI.

666 stars
0 votes
0 copies
3 views
Added February 8, 2026

toolsbashgit

Works with

Security analysis

A100/100

Scanned February 12, 2026

npx -y skills add majiayu000/claude-skill-registry --skill github-ops --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Github Ops?

Add the live security badge to your README. It updates with every re-scan.

[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/majiayu000-github-ops/badge)](https://www.skillsdirectory.com/skills/majiayu000-github-ops)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro

SKILL.md

---
name: github-ops
description: GitHub operations wrapper. Helps manage PRs, Issues, and Reviews efficiently via CLI.
version: 1.0
model: sonnet
invoked_by: both
user_invocable: true
tools: [Bash, Read]
best_practices:
  - Use gh CLI for all operations
  - Restrict JSON output to relevant fields
  - Verify authentication before operations
error_handling: graceful
streaming: supported
---

# GitHub Ops Skill

## 🛠️ CLI Tools

We use `gh` (GitHub CLI) for all operations.

## 📋 Pull Requests

### Create PR

```bash
git push -u origin feature-branch
gh pr create --title "feat: description" --body "Summary of changes..."
```

### Checkout PR

```bash
gh pr checkout <number>
```

### Review PR

```bash
gh pr diff
gh pr review --approve
```

## 🐛 Issues

### List Issues

```bash
gh issue list --limit 5
```

### Create Issue

```bash
gh issue create --title "Bug: ..." --body "Reproduction steps..."
```

## 🤖 Context Optimization

Instead of dumping the entire JSON of an issue, use:

```bash
gh issue view <number> --json title,body,comments
```

This restricts the output to relevant fields only.

## Memory Protocol (MANDATORY)

**Before starting:**
Read `.claude/context/memory/learnings.md`

**After completing:**

- New pattern -> `.claude/context/memory/learnings.md`
- Issue found -> `.claude/context/memory/issues.md`
- Decision made -> `.claude/context/memory/decisions.md`

> ASSUME INTERRUPTION: If it's not in memory, it didn't happen.