github-mcp

Validates GitHub MCP targets and separates remote from local git operations.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/nowonbun/nowonbun-harness --skill github-mcp-nowonbun
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-mcp
Source: https://github.com/nowonbun/nowonbun-harness/tree/main/codex-skills/tool-usage-management_github-mcp
Command: npx skills add https://github.com/nowonbun/nowonbun-harness --skill github-mcp-nowonbun

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures clear separation between GitHub MCP (remote API actions) and local git operations, reducing miswrites and misconfigurations by validating targets before any remote change.

Core Features & Use Cases

  • Target validation: Verifies owner, repo, and target identifiers before any GitHub MCP write.
  • Role separation: Clearly distinguishes remote MCP actions from local version-control actions within a workspace.
  • Safety-first governance: Enforces pre-checks, explicit reporting, and bounds checking to prevent unintended changes.

Quick Start

Instruct the AI to validate the repository context and target IDs before performing any GitHub MCP operation.

Frequently Asked Questions about github-mcp

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

FAQPage Schema
How do I safely manage GitHub MCP remote writes without affecting local git operations?

To safely manage GitHub MCP remote writes, enforce target validation and clear role separation to prevent mixing local git actions with remote API operations. This delineates version-control work from MCP updates, reducing miswrites.

What is target validation for GitHub MCP operations?

Target validation for GitHub MCP verifies owner, repo, and target identifiers before any remote write. This safety-first governance ensures explicit bounds checking to prevent unintended changes to repositories.

How do I prevent unintended repository updates when using GitHub MCP?

Prevent unintended repository updates by mandating read-before-write checks and post-operation reporting. This enforces pre-checks on owner and repo targets before executing issue, PR, or file operations.

Does GitHub MCP work with local git workflows in the same workspace?

GitHub MCP can work alongside local git workflows by enforcing strict role separation within a controlled workspace. This clearly distinguishes remote MCP actions from local version-control actions to prevent misconfigurations.

When do I need to validate repository context for GitHub MCP actions?

Validate repository context before performing any GitHub MCP operation such as issue, PR, review, branch, or file actions. This ensures owner and repo target IDs are verified before remote changes occur.

What are the limitations of using GitHub MCP for remote repository actions?

GitHub MCP for remote repository actions requires explicit target validation and does not mix with local git commands. Operations are bounded by pre-checks and post-operation reporting to maintain safety.