ush-github-task-flow

Carry a bounded task from GitHub issue through branch, validation, and pull request.

Updated Sep 5, 2026
One-click install
npx skills add https://github.com/edward321416-maker/universal-skill-hub --skill ush-github-task-flow-edward321416-maker
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ush-github-task-flow
Source: https://github.com/edward321416-maker/universal-skill-hub/tree/main/adapters/claude-code/ush-github-task-flow
Command: npx skills add https://github.com/edward321416-maker/universal-skill-hub --skill ush-github-task-flow-edward321416-maker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It prevents untracked, unsafe repository changes by enforcing a disciplined GitHub workflow where every task is recorded in an issue, implemented on an isolated branch, validated, and delivered as a pull request — with merging treated as a separate, explicitly authorized operation. ## Core Features & Use Cases - Issue-to-PR workflow: Resolves or creates a tracking issue, creates an isolated branch from origin/main, implements only the scoped work, validates changes, and opens a review-ready PR. - Gated merge operation: Merging is a distinct operation requiring its own explicit request and a specifically granted merge permission, never implied by a request to deliver a PR. - Safety contract: Prohibits direct commits to main, plain force-pushes, history rewrites on shared branches, and bypassing required checks or reviews. - Use Case: A user asks to implement issue #42 and open a PR; the skill reuses the existing issue, branches as issue/42-short-slug, runs the relevant tests, opens the PR, and reports merge readiness without merging. ## Quick Start Implement GitHub issue #42 on an isolated branch, run the relevant tests, and open a pull request without merging it.

Frequently Asked Questions about ush-github-task-flow

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

FAQPage Schema
How do I implement a GitHub issue and open a pull request?▼

Resolve the existing tracking issue, create an isolated branch from origin/main named after the issue, implement only the scoped work, run the relevant tests, then push and open a PR against main with a body stating the result and verification.

Does this workflow merge the pull request automatically?▼

No. Delivering a PR and merging it are separate operations. Merging requires its own explicit request and a specifically granted merge permission, plus confirmation that required checks and approvals are green.

Can I use this with a read-only GitHub token?▼

No. The skill requires an actual write-capable GitHub provider, such as gh authenticated with write access. A read-only provider blocks the workflow regardless of host-level permission settings.

When should I not use this GitHub task workflow?▼

Do not use it for read-only git questions, explaining git concepts, inspecting a commit without changes, or reviewing an existing PR without also being asked to change something.

Is force-pushing allowed when rebasing a PR branch?▼

Plain git push --force is never allowed. Use --force-with-lease only on a branch owned solely by this task, after confirming no one else is building on its current tip, and never on shared branches.