How do I install the Github Operations skill?

Run npx skillmds@latest add rom-orlovich/github-operations-2 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 Operations safe to use?

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

Which AI agents work with Github Operations?

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

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

Who published Github Operations?

rom-orlovich (@rom-orlovich) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Github Operations by rom-orlovich — Agent Skill

Name: Github Operations
Rating: 4.666666666666667 (3 reviews)
Author: rom-orlovich

File contents

GitHub operations using MCP tools for API interactions and local git commands for repository management.

IMPORTANT: Always use MCP tools (github:*) for API operations. Use local git commands for repository management only.

Quick Reference

Workflow: See flow.md for complete workflow guide and templates

Key Principles

Always use MCP tools (github:*) for API operations
Use local git commands for repository management
Post responses using MCP tools after task completion

Environment

GITHUB_TOKEN - GitHub personal access token (required for MCP authentication)

MCP Operations

Always use MCP tools for GitHub API operations:

github:get_file_content - Get file contents
github:search_code - Search code across repositories
github:create_pull_request - Create PRs
github:add_issue_comment - Post comments on issues/PRs
github:get_pull_request - Get PR details
github:create_or_update_file - Commit file changes

MCP tools are documented in flow.md with examples.

Repository Workflow

Repositories are pre-cloned by Docker at startup (via GITHUB_REPOS env var). If repository doesn't exist, clone it first.

Workflow: Check repository → Update (git pull) → Create feature branch → Make changes → Commit → Push → Create PR

Branch naming: fix/issue-123, feature/add-auth, refactor/cleanup-module

See flow.md for complete workflow details.

Response Posting

IMPORTANT: Always post responses after task completion using github:add_issue_comment.

See flow.md for workflow examples and templates.md for response templates.

Workflows

See flow.md for complete workflow examples including:

Complexity-based approach selection (MCP tools vs cloned repository)
Repository management
Creating pull requests
Posting responses

---name: github-operations-2description: GitHub API operations and repository workflow for issues, PRs, commits, and branch management. Use when working with GitHub repositories, creating issues/PRs, posting comments, or managing repository workflows.---GitHub operations using MCP tools for API interactions and local git commands for repository management.> **IMPORTANT:** Always use MCP tools (`github:*`) for API operations. Use local git commands for repository management only.## Quick Reference- **Workflow**: See [flow.md](flow.md) for complete workflow guide and templates## Key Principles1. **Always use MCP tools** (`github:*`) for API operations2. **Use local git commands** for repository management3. **Post responses** using MCP tools after task completion## Environment- `GITHUB_TOKEN` - GitHub personal access token (required for MCP authentication)## MCP Operations**Always use MCP tools for GitHub API operations:**- `github:get_file_content` - Get file contents- `github:search_code` - Search code across repositories- `github:create_pull_request` - Create PRs- `github:add_issue_comment` - Post comments on issues/PRs- `github:get_pull_request` - Get PR details- `github:create_or_update_file` - Commit file changes**MCP tools are documented in [flow.md](flow.md) with examples.**## Repository WorkflowRepositories are pre-cloned by Docker at startup (via `GITHUB_REPOS` env var). If repository doesn't exist, clone it first.**Workflow:** Check repository → Update (`git pull`) → Create feature branch → Make changes → Commit → Push → Create PR**Branch naming:** `fix/issue-123`, `feature/add-auth`, `refactor/cleanup-module`See [flow.md](flow.md) for complete workflow details.### Response Posting**IMPORTANT**: Always post responses after task completion using `github:add_issue_comment`.See [flow.md](flow.md) for workflow examples and [templates.md](templates.md) for response templates.## WorkflowsSee [flow.md](flow.md) for complete workflow examples including:- Complexity-based approach selection (MCP tools vs cloned repository)- Repository management- Creating pull requests- Posting responses

Frequently asked questions

Github Operations