github-publish-changes

Commit, push, and open draft pull requests for scoped local changes on GitHub.

5.3k|976|Updated Aug 25, 2025
One-click install
npx skills add https://github.com/Devin-AXIS/iPolloWork --skill github-publish-changes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-publish-changes
Source: https://github.com/Devin-AXIS/iPolloWork/tree/main/examples/plugin-packages/github/skills/github-publish-changes
Command: npx skills add https://github.com/Devin-AXIS/iPolloWork --skill github-publish-changes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Publishing local work to GitHub involves many error-prone steps: identifying the right files in a mixed worktree, branching correctly, staging only intended changes, and opening a pull request. This Skill enforces a disciplined, safe workflow so nothing unrelated gets committed or pushed.

Core Features & Use Cases

  • Scoped Staging: Inspects git status and diffs to stage only the files belonging to the current task, never defaulting to git add -A without confirmed scope.
  • Branch Management: Creates an agent/<short-description> branch when on the default branch, or keeps the intended feature branch.
  • Draft Pull Request Creation: Pushes with upstream tracking and calls create-pull-request through the connected GitHub service, keeping the PR as a draft unless a ready-for-review PR is explicitly requested.
  • Use Case: After an agent finishes editing three source files in a repo with other unrelated local changes, use this Skill to stage only those files, commit them on a new branch, push, and open a draft PR for review.

Quick Start

Commit my current changes for this task, push them on a new branch, and open a draft pull request on GitHub.

Frequently Asked Questions about github-publish-changes

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

FAQPage Schema
How do I commit and push only specific files in a mixed git worktree?

Inspect git status and the full diff to identify which changes belong to the task, then stage explicit file paths rather than using git add -A. Review the staged diff before committing to confirm no unrelated changes are included.

How do I create a draft pull request on GitHub from an agent workflow?

Push the current branch with upstream tracking, resolve the repository owner, repo name, default branch, and head branch, then call create-pull-request through the connected GitHub service with draft set to true.

When should I create a new branch instead of committing to the default branch?

Create a new branch whenever you are currently on the repository's default branch. This Skill creates an agent/<short-description> branch in that case, and keeps the existing branch when already on an intended feature branch.

Can this Skill force-push, merge, or delete branches?

No. Force-pushing, deleting branches, merging, and rewriting history are prohibited unless the user explicitly requests them. The Skill only stages, commits, pushes with upstream tracking, and opens pull requests.

Why does the pull request stay as a draft by default?

Draft status signals the changes still need human review before merging. The PR is only marked ready-for-review when the user explicitly requests it, reducing the risk of premature merges.