Run any Skill in Manus with one click

Get Started

ship-pr

Stars2

Forks0

UpdatedJune 25, 2026 at 09:21

Ship current work through a GitHub pull request using git and gh.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

haolamnm

haolamnm/moodle-mcp-srv

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	ship-pr
description	Ship current work through a GitHub pull request using git and gh.
metadata	{"author":"haolamnm","version":"0.1.0"}

Ship PR

Use when the user says /ship-pr, "open a PR", "ship this branch", or asks to move completed work into review.

Preconditions

Requires git and authenticated gh CLI.
Never push directly to main.
Never force-push unless the user explicitly asks.
Never commit, push, or open a PR with private Moodle data, tokens, .env, or local MCP/client configs.

Workflow

Inspect state:
- git status --short
- git branch --show-current
- git remote -v
- gh auth status
If on main, stop and create or ask for a feature branch before shipping.
If dirty, group changes into atomic Conventional Commit proposals. Ask before committing.
Fetch and compare with main:
- git fetch origin main
- git log origin/main..HEAD --oneline
- git diff origin/main...HEAD --stat
Run relevant checks from CONTRIBUTING.md. At minimum run lint/type checks and targeted tests for touched code.
Read .github/pull_request_template.md and draft a concise PR body from real commits, diff, and checks.
Push the branch with git push origin <branch>.
Create the PR with gh pr create --base main --head <branch> --title "<conventional title>" --body "<body>".
Report the PR URL, branch, commits, checks run, and any remaining risks.

PR Body Rules

Follow the repo PR template.
Include concrete verification commands and outcomes.
Mention skipped checks explicitly.
Keep Moodle examples generic; never include live course names, grades, submissions, users, private URLs, or tokens.

Blockers

Block shipping when checks fail, the branch contains unrelated private/local files, commits are WIP/debug-only, gh is unauthenticated, or the diff includes unreviewed generated churn.

More from this repository

same repository

changelog

haolamnm/moodle-mcp-srv

Maintain CHANGELOG.md as meaningful merges land. Use after merging a feature branch, before cutting a release, or when asked "what changed?".

2026-06-252

release

haolamnm/moodle-mcp-srv

Cut a GitHub release by updating changelog, validating release checks, creating a tag, and publishing with gh.

2026-06-252

adr

haolamnm/moodle-mcp-srv

Record durable architectural decisions in docs/adr with compact context and consequences.

2026-06-252

codebase-design

haolamnm/moodle-mcp-srv

Shared vocabulary for designing deep modules, interfaces, seams, and adapters.

2026-06-252

diagnosing-bugs

haolamnm/moodle-mcp-srv

Diagnose hard bugs by building a tight repro loop before changing code.

2026-06-252

domain-modeling

haolamnm/moodle-mcp-srv

Maintain Moodle MCP domain language and update CONTEXT.md only when terminology is resolved.

2026-06-252

name	ship-pr
description	Ship current work through a GitHub pull request using git and gh.
metadata	{"author":"haolamnm","version":"0.1.0"}

Ship PR

Use when the user says /ship-pr, "open a PR", "ship this branch", or asks to move completed work into review.

Preconditions

Requires git and authenticated gh CLI.
Never push directly to main.
Never force-push unless the user explicitly asks.
Never commit, push, or open a PR with private Moodle data, tokens, .env, or local MCP/client configs.

Workflow

Inspect state:
- git status --short
- git branch --show-current
- git remote -v
- gh auth status
If on main, stop and create or ask for a feature branch before shipping.
If dirty, group changes into atomic Conventional Commit proposals. Ask before committing.
Fetch and compare with main:
- git fetch origin main
- git log origin/main..HEAD --oneline
- git diff origin/main...HEAD --stat
Run relevant checks from CONTRIBUTING.md. At minimum run lint/type checks and targeted tests for touched code.
Read .github/pull_request_template.md and draft a concise PR body from real commits, diff, and checks.
Push the branch with git push origin <branch>.
Create the PR with gh pr create --base main --head <branch> --title "<conventional title>" --body "<body>".
Report the PR URL, branch, commits, checks run, and any remaining risks.

PR Body Rules

Follow the repo PR template.
Include concrete verification commands and outcomes.
Mention skipped checks explicitly.
Keep Moodle examples generic; never include live course names, grades, submissions, users, private URLs, or tokens.

Blockers

Block shipping when checks fail, the branch contains unrelated private/local files, commits are WIP/debug-only, gh is unauthenticated, or the diff includes unreviewed generated churn.