github-operations

Manage GitHub repository cloning, worktrees, conventional commits, and pull requests.

Updated Mar 8, 2026
One-click install
npx skills add https://github.com/gman-robotics/gmr-deerflow --skill github-operations-gman-robotics
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-operations
Source: https://github.com/gman-robotics/gmr-deerflow/tree/main/skills/public/github-operations
Command: npx skills add https://github.com/gman-robotics/gmr-deerflow --skill github-operations-gman-robotics

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires PyJWT, cryptography, requests, and includes scripts (resource) components.

What problem does it solve?

This Skill automates the entire lifecycle of GitHub operations, from cloning repositories and managing branches to creating commits and pull requests, significantly reducing manual effort and ensuring consistency.

Core Features & Use Cases

  • Automated Cloning & Worktrees: Clones repositories once and uses worktrees for isolated task branches, keeping the main clone clean.
  • Conventional Commits: Enforces the conventional commit format for structured and understandable commit history.
  • PR Creation & Review: Streamlines the process of creating pull requests with detailed descriptions and facilitates code review actions.
  • Use Case: A developer needs to implement a new feature. This Skill can clone the repository, create a new worktree and branch, allow the developer to make changes, commit them using conventional commits, push the branch, and create a pull request for review.

Quick Start

Use the github-operations skill to clone the repository at 'https://github.com/owner/repo.git' and create a new branch named 'feat/my-task-description'.

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 request creation and enforce conventional commits?

Automating GitHub pull request creation involves cloning repositories, creating isolated worktrees, committing changes using conventional commit formats, and pushing branches to generate pull requests. This ensures structured history and consistent review processes.

What is the best way to manage isolated task branches for GitHub automation?

Managing isolated task branches uses git worktrees linked to a single cloned repository. This keeps the main clone clean while allowing parallel feature development, ensuring isolated environments for automated commits and pull requests.

Does automating GitHub operations require GitHub App installation tokens?

Yes, automating GitHub operations securely requires GitHub App installation tokens. These tokens provide short-lived, authenticated access within a sandboxed environment, utilizing the 'git' and 'gh' CLI tools to manage repository lifecycles safely.

Can I use the gh CLI to streamline code review workflows?

Yes, you can use the 'gh' CLI to streamline code review workflows. It facilitates code review actions and automates pull request creation with detailed descriptions, directly integrating with cloned repositories and isolated worktrees.

Why use conventional commits in automated CI/CD pipelines?

Using conventional commits in automated CI/CD pipelines enforces a structured and understandable commit history. It streamlines automated pull request creation and review processes by providing consistent formatting for repository lifecycle management.