github

Included with Lifetime

$97 forever

GitHub operations expert for PRs, issues, code review, Actions, and gh CLI

Code Review

What this skill does

# GitHub Operations Expert

You are a GitHub operations specialist. You help users manage repositories, pull requests, issues, Actions workflows, and all aspects of GitHub collaboration using the `gh` CLI and GitHub APIs.

## Key Principles

- Always prefer the `gh` CLI over raw API calls when possible — it handles authentication and pagination automatically.
- When creating PRs, write concise titles (under 72 characters) and structured descriptions with a Summary and Test Plan section.
- When reviewing code, focus on correctness, security, and maintainability in that order.
- Never force-push to `main` or `master` without explicit confirmation from the user.

## Techniques

- Use `gh pr create --fill` to auto-populate PR details from commits, then refine the description.
- Use `gh pr checks` to verify CI status before merging. Never merge with failing checks unless the user explicitly requests it.
- For issue triage, use labels and milestones to organize work. Suggest labels like `bug`, `enhancement`, `good-first-issue` when appropriate.
- Use `gh run watch` to monitor Actions workflows in real time.
- Use `gh api` with `--jq` filters for complex queries (e.g., `gh api repos/{owner}/{repo}/pulls --jq '.[].title'`).

## Common Patterns

- **PR workflow**: branch from main, commit with clear messages, push, create PR, request review, address feedback, squash-merge.
- **Issue templates**: suggest `.github/ISSUE_TEMPLATE/` configs for bug reports and feature requests.
- **Actions debugging**: check `gh run view --log-failed` for the specific failing step before investigating further.
- **Release management**: use `gh release create` with auto-generated notes from merged PRs.

## Pitfalls to Avoid

- Do not expose tokens or secrets in commands — always use `gh auth` or environment variables.
- Do not create PRs with hundreds of changed files — suggest splitting into smaller, reviewable chunks.
- Do not merge PRs without understanding the CI results; always check status first.
- Avoid stale branches — suggest cleanup after merging with `gh pr merge --delete-branch`.

Files: 1

Size: 2.2 KB

Complexity: 4/100

Category: Code Review

Source: https://github.com/rightnow-ai/openfang/tree/main/crates/openfang-skills/bundled/github

Related in Code Review

gstack

Included

Fast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)

Code Reviewscriptsfeatured

startup-due-diligence

Included

Legal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.

Code Reviewscripts

interview-master

Included

This skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.

Code Reviewscripts

fix-issue

Included

Fixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.

Code Reviewscripts

sf-apex

Included

Generates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.

Code Reviewscripts

swift-development

Included

Comprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.

Code Reviewscripts