github-ops — for Claude Code github-ops, ImpactMojo, community, for Claude Code, ide skills, bct-taxonomy, behavior-change, certificates, development, education

v1.0.0

Sobre este Skill

Cenario recomendado: Ideal for AI agents that need github operations skill. Resumo localizado: ImpactMojo — Free development education for social impact. It covers bct-taxonomy, behavior-change, certificates workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

Recursos

GitHub Operations Skill
Perform GitHub API operations using $GITHUB PAT for any repository the token has access to.
All API calls use:
Authorization: token $GITHUB PAT
Base URL: https://api.github.com

# Core Topics

Varnasr Varnasr
[1]
[1]
Updated: 3/23/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 10/11

This page remains useful for teams, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution Quality floor passed for review
Review Score
10/11
Quality Score
58
Canonical Locale
en
Detected Body Locale
en

Cenario recomendado: Ideal for AI agents that need github operations skill. Resumo localizado: ImpactMojo — Free development education for social impact. It covers bct-taxonomy, behavior-change, certificates workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

Por que usar essa habilidade

Recomendacao: github-ops helps agents github operations skill. ImpactMojo — Free development education for social impact. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

Melhor para

Cenario recomendado: Ideal for AI agents that need github operations skill.

Casos de Uso Práticos for github-ops

Caso de uso: Applying GitHub Operations Skill
Caso de uso: Applying Perform GitHub API operations using $GITHUB PAT for any repository the token has access to
Caso de uso: Applying All API calls use:

! Segurança e Limitações

  • Limitacao: Requires repository-specific context from the skill documentation
  • Limitacao: Works best when the underlying tools and dependencies are already configured

Why this page is reference-only

  • - Current locale does not satisfy the locale-governance contract.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is github-ops?

Cenario recomendado: Ideal for AI agents that need github operations skill. Resumo localizado: ImpactMojo — Free development education for social impact. It covers bct-taxonomy, behavior-change, certificates workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

How do I install github-ops?

Run the command: npx killer-skills add Varnasr/ImpactMojo/github-ops. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for github-ops?

Key use cases include: Caso de uso: Applying GitHub Operations Skill, Caso de uso: Applying Perform GitHub API operations using $GITHUB PAT for any repository the token has access to, Caso de uso: Applying All API calls use:.

Which IDEs are compatible with github-ops?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for github-ops?

Limitacao: Requires repository-specific context from the skill documentation. Limitacao: Works best when the underlying tools and dependencies are already configured.

How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add Varnasr/ImpactMojo/github-ops. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use github-ops immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

github-ops

ImpactMojo — Free development education for social impact. It covers bct-taxonomy, behavior-change, certificates workflows. This AI agent skill supports

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

GitHub Operations Skill

Perform GitHub API operations using $GITHUB_PAT for any repository the token has access to.

Authentication

All API calls use:

Authorization: token $GITHUB_PAT

Base URL: https://api.github.com

Capabilities

Pull Requests

  • Create PRs: POST /repos/{owner}/{repo}/pulls
  • Merge PRs: PUT /repos/{owner}/{repo}/pulls/{number}/merge
  • List/review PRs: GET /repos/{owner}/{repo}/pulls
  • Add reviewers: POST /repos/{owner}/{repo}/pulls/{number}/requested_reviewers
  • Comment on PRs: POST /repos/{owner}/{repo}/issues/{number}/comments

Issues

  • Create issues: POST /repos/{owner}/{repo}/issues
  • Close issues: PATCH /repos/{owner}/{repo}/issues/{number} with {"state": "closed"}
  • Label issues: POST /repos/{owner}/{repo}/issues/{number}/labels
  • Assign issues: POST /repos/{owner}/{repo}/issues/{number}/assignees

Releases

  • Create release: POST /repos/{owner}/{repo}/releases
  • List releases: GET /repos/{owner}/{repo}/releases

Branch Management

  • List branches: GET /repos/{owner}/{repo}/branches
  • Delete branch: DELETE /repos/{owner}/{repo}/git/refs/heads/{branch}
  • Branch protection: PUT /repos/{owner}/{repo}/branches/{branch}/protection

Usage Pattern

Always use curl with the PAT:

bash
1curl -s -H "Authorization: token $GITHUB_PAT" \ 2 -H "Accept: application/vnd.github.v3+json" \ 3 https://api.github.com/repos/{owner}/{repo}/endpoint

For POST/PATCH/PUT, add -X METHOD -d '{"key": "value"}'.

Labels

  • List labels: GET /repos/{owner}/{repo}/labels
  • Create label: POST /repos/{owner}/{repo}/labels with {"name": "...", "color": "...", "description": "..."}
  • Add labels to issue/PR: POST /repos/{owner}/{repo}/issues/{number}/labels with {"labels": ["label1", "label2"]}

Auto-Labeling PRs

When creating PRs, automatically apply labels based on changed files:

Path PatternLabelColor
Games/*games10B981
courses/*courses6366F1
blog/*blogEC4899
BookSummaries/*book-summariesD97706
Handouts/*handoutsF59E0B
dojos*dojos0EA5E9
.claude/*claude-setup94A3B8
data/*data64748B
docs/*documentation0284C7

Workflow:

  1. Before labeling, check if label exists: GET /repos/{owner}/{repo}/labels/{name}
  2. If 404, create it with the color above
  3. Then apply to the PR/issue

Best Practices

  • Always check if a PR/issue exists before creating duplicates
  • Include meaningful titles and descriptions
  • Link PRs to issues with "Closes #N" in the body
  • Never force-push to main/master
  • Auto-label PRs based on changed file paths (see table above)
  • Prefer the API over gh CLI for reliability in remote environments

Habilidades Relacionadas

Looking for an alternative to github-ops or another community skill for your workflow? Explore these related open-source skills.

Ver tudo

openclaw-release-maintainer

Logo of openclaw
openclaw

Resumo localizado: 🦞 # OpenClaw Release Maintainer Use this skill for release and publish-time workflow. It covers ai, assistant, crustacean workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

widget-generator

Logo of f
f

Resumo localizado: Generate customizable widget plugins for the prompts.chat feed system # Widget Generator Skill This skill guides creation of widget plugins for prompts.chat . It covers ai, artificial-intelligence, awesome-list workflows. This AI agent skill supports Claude Code, Cursor, and

flags

Logo of vercel
vercel

Resumo localizado: The React Framework # Feature Flags Use this skill when adding or changing framework feature flags in Next.js internals. It covers blog, browser, compiler workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

138.4k
0
Navegador

pr-review

Logo of pytorch
pytorch

Resumo localizado: Usage Modes No Argument If the user invokes /pr-review with no arguments, do not perform a review . It covers autograd, deep-learning, gpu workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

98.6k
0
Desenvolvedor