github-write

Select between gh and Connector for GitHub issue and PR updates.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/ebijun1007/vibe-coding --skill github-write
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-write
Source: https://github.com/ebijun1007/vibe-coding/tree/main/.codex/skills/github-write
Command: npx skills add https://github.com/ebijun1007/vibe-coding --skill github-write

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Updating GitHub issues and PRs can be error-prone when choosing between gh and Connector; this skill clarifies the most efficient method to perform updates with minimal friction.

Core Features & Use Cases

  • Decision guide for when to use gh versus Connector for comments, labels, state, and body updates.
  • Safe fallback to require minimal permissions while enabling structured updates.
  • Use Case: When you need to update multiple issues with uniform labels across a batch.

Quick Start

Choose the most efficient update method for a GitHub issue or PR.

Frequently Asked Questions about github-write

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

FAQPage Schema
How do I update GitHub issues and pull requests efficiently?

Efficiently updating GitHub issues and pull requests involves selecting between gh and Connector based on the update type, enforcing a policy that uses gh for straightforward writes and Connector for structured updates.

When should I use gh versus Connector to modify GitHub issue labels and comments?

Use gh for straightforward writes like simple label or comment additions, and switch to Connector when you need structured updates across issues or pull requests, ensuring minimal permissions while enabling complex modifications.

What is the best way to batch update multiple GitHub issues with uniform labels?

The best way to batch update multiple GitHub issues with uniform labels is by using the Connector for structured updates, which enforces a safe fallback policy to require minimal permissions while applying changes across typical development workflows.

What happens if gh fails while updating a GitHub pull request?

If gh fails while updating a GitHub pull request, the system enforces a sandbox fallback policy, switching to an alternative method to ensure the update completes safely with minimal required permissions.

Can I update the body and state of GitHub issues using both gh and Connector?

Yes, you can update the body and state of GitHub issues using both gh and Connector, with the skill guiding you to use gh for straightforward body or state writes and Connector for structured modifications.