github-operations

Automate GitHub repository management, commits, and pull requests via GitHubREST functions.

3|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/transreal/claudecode --skill github-operations-transreal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-operations
Source: https://github.com/transreal/claudecode/tree/main/Claude%20Directives/skills/github-operations
Command: npx skills add https://github.com/transreal/claudecode --skill github-operations-transreal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual, error-prone work of performing common GitHub tasks from scratch by mapping natural-language requests to the correct ClaudeDecode GitHubREST functions with strong safety guardrails.

Core Features & Use Cases

  • Repository lifecycle management: Create or ensure a local repo, derive package URLs, and manage a repo/manifest workspace.
  • Commit, refresh, and upload: Commit package changes and refresh/commit with options for branching and upload behavior.
  • Pull request workflow: Create PRs, list/review/merge/close PRs, and review commits safely (including button re-execution prevention).
  • Install/update from GitHub: Install new packages or update existing ones using GitHubREST (with explicit owner handling for external repositories).
  • No web browsing policy: Enforces “no web search” for GitHub actions so the GitHubREST package is the single source of truth.

Quick Start

Use the github-operations skill to open a pull request for updating package changes when you tell the AI: "Create a PR for package fib with a clear title and body, and include the latest updates."

Frequently Asked Questions about github-operations

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate GitHub pull requests from natural language instructions?

Automating GitHub pull requests involves mapping natural-language instructions to GitHubREST functions to create, review, and merge PRs safely. This enforces guard rules and prevents button re-execution errors for reliable commit workflow execution.

Can I install and update packages directly from GitHub repositories without web browsing?

Installing and updating packages from GitHub requires using GitHubREST functions as the single source of truth, explicitly handling external repository owners. A strict no web search policy ensures package installation relies only on valid local manifest paths.

What is the best way to manage repository creation and commit workflows programmatically?

Repository creation and commit workflows are best managed by mapping instructions to GitHubREST functions for local repo setup, branching, and uploading. This approach applies safety guardrails to prevent manual errors during package changes and repository maintenance.

Does GitHubREST support local manifest and clone paths for repository lifecycle management?

GitHubREST supports local manifest and clone paths for repository lifecycle management by deriving package URLs and managing workspaces locally. It requires using only valid function names from repository docs to ensure reliable execution.

Why does my GitHub repository management task fail when using web search?

GitHub repository management tasks fail with web search because a strict no web browsing policy is enforced, making GitHubREST the sole source of truth. This constraint ensures safe execution by avoiding invalid external function calls or unverified data.