github-operations

Manage GitHub repositories through Git CLI operations with branch protection and commit conventions.

4|2|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/Arete-Consortium/ai-skills --skill github-operations-arete-consortium
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-operations
Source: https://github.com/Arete-Consortium/ai-skills/tree/main/agents/integrations/github-operations
Command: npx skills add https://github.com/Arete-Consortium/ai-skills --skill github-operations-arete-consortium

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Performing git and GitHub operations without guardrails leads to force-pushed shared branches, committed secrets, and direct pushes to main. This Skill enforces branch protection, conventional commits, and credential hygiene across every repository operation. ## Core Features & Use Cases - Full Repository Lifecycle: Clone, pull, branch, commit, and push with typed inputs, risk levels, and post-execution verification for each operation. - Issue and PR Management: Create GitHub issues and pull requests, then merge only after required reviews and CI checks pass. - Security Controls: Pre-commit secret scanning checklists, protected branch rules, and escalation ladders for auth failures, merge conflicts, and CI failures. - Use Case: After editing files in a feature branch, ask the agent to commit with a conventional message, push the branch, and open a pull request with a summary and test plan — all without risking a direct push to main. ## Quick Start Ask the agent to create a feature branch from main, commit your staged changes with a conventional commit message, push the branch, and open a pull request against main.

Frequently Asked Questions about github-operations

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

FAQPage Schema
How do I create a pull request from the command line with GitHub CLI?▼

Use the create_pull_request operation with the repository in owner/repo format, a title under 70 characters, a markdown body with summary and test plan, and the head branch. The skill verifies creation and waits for CI checks before requesting review.

How to commit changes with conventional commit messages in git?▼

Stage and commit using the type(scope): subject format, such as feat(auth): add OAuth2 login support. The skill requires reviewing the diff first and verifies no secrets were committed against .gitignore patterns afterward.

Can I push directly to the main branch with this skill?▼

No. Protected branches (main, master, production, release/*) require pull requests, passing CI checks, and code review approval. Direct pushes and force pushes to protected branches are blocked by the skill's constraints.

What happens when a git pull causes merge conflicts?▼

The skill reports the conflicting files and does not auto-resolve them. It pauses and waits for your resolution guidance, since automatic conflict resolution risks losing intended changes.

What credentials does GitHub CLI automation need?▼

A GITHUB_TOKEN environment variable holding a Personal Access Token with minimum required scopes, plus git and gh CLI installed. Tokens should rotate every 90 days and never be hardcoded or committed.

When should I not use this skill for git operations?▼

Avoid it for non-GitHub HTTP API calls (use an API client), arbitrary shell commands unrelated to git, direct file editing, or code search. Those tasks do not need branch protection or commit convention controls.