Run any Skill in Manus with one click

yeet

Stars2

Forks1

UpdatedMarch 22, 2026 at 15:03

Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`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

duggal1

duggal1/Sapphire-cli

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

File Explorer

5 files

SKILL.md

readonly

name	yeet
description	Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).

Prerequisites

Require GitHub CLI gh. Check gh --version. If missing, ask the user to install gh and stop.
Require authenticated gh session. Run gh auth status. If not authenticated, ask the user to run gh auth login (and re-run gh auth status) before continuing.

Naming conventions

Branch: codex/{description} when starting from main/master/default.
Commit: {description} (terse).
PR title: [codex] {description} summarizing the full diff.

Workflow

If on main/master/default, create a branch: git checkout -b "codex/{description}"
Otherwise stay on the current branch.
Confirm status, then stage everything: git status -sb then git add -A.
Commit tersely with the description: git commit -m "{description}"
Run checks if not already. If checks fail due to missing deps/tools, install dependencies and rerun once.
Push with tracking: git push -u origin $(git branch --show-current)
If git push fails due to workflow auth errors, pull from master and retry the push.
Open a PR and edit title/body to reflect the description and the deltas: GH_PROMPT_DISABLED=1 GIT_TERMINAL_PROMPT=0 gh pr create --draft --fill --head $(git branch --show-current)
Write the PR description to a temp file with real newlines (e.g. pr-body.md ... EOF) and run pr-body.md to avoid \n-escaped markdown.
PR description (markdown) must be detailed prose covering the issue, the cause and effect on users, the root cause, the fix, and any tests or checks used to validate.

More from this repository

same repository

harness

duggal1/Sapphire-cli

Builds or restructures a Sapphire harness. Use when a task needs a strict multi-agent workflow, reusable project skills, or a stronger orchestration design for non-trivial work.

2026-04-012

elite-backend-engineering

duggal1/Sapphire-cli

Design and implement production-grade backend systems with strict contracts, clear boundaries, strong validation, disciplined testing, observability, resilience, and maintainable architecture across languages and frameworks.

2026-03-292

gh-issues

duggal1/Sapphire-cli

Fetch GitHub issues, spawn sub-agents to implement fixes and open PRs, then monitor and address PR review comments. Usage: /gh-issues [owner/repo] [--label bug] [--limit 5] [--milestone v1.0] [--assignee @me] [--fork user/repo] [--watch] [--interval 5] [--reviews-only] [--cron] [--dry-run] [--model glm-5] [--notify-channel -1002381931352]

2026-03-292

gh-fix-ci

duggal1/Sapphire-cli

Use when a user asks to debug or fix failing GitHub PR checks that run in GitHub Actions; use `gh` to inspect checks and logs, summarize failure context, draft a fix plan, and implement only after explicit approval. Treat external providers (for example Buildkite) as out of scope and report only the details URL.

2026-03-222

teach-impeccable

duggal1/Sapphire-cli

One-time setup that gathers design context for your project and saves it to your AI config file. Run once to establish persistent design guidelines.

2026-03-222

adapt

duggal1/Sapphire-cli

Adapt designs to work across different screen sizes, devices, contexts, or platforms. Ensures consistent experience across varied environments.

2026-03-222

name	yeet
description	Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).

Prerequisites

Require GitHub CLI gh. Check gh --version. If missing, ask the user to install gh and stop.
Require authenticated gh session. Run gh auth status. If not authenticated, ask the user to run gh auth login (and re-run gh auth status) before continuing.

Naming conventions

Branch: codex/{description} when starting from main/master/default.
Commit: {description} (terse).
PR title: [codex] {description} summarizing the full diff.

Workflow

If on main/master/default, create a branch: git checkout -b "codex/{description}"
Otherwise stay on the current branch.
Confirm status, then stage everything: git status -sb then git add -A.
Commit tersely with the description: git commit -m "{description}"
Run checks if not already. If checks fail due to missing deps/tools, install dependencies and rerun once.
Push with tracking: git push -u origin $(git branch --show-current)
If git push fails due to workflow auth errors, pull from master and retry the push.
Open a PR and edit title/body to reflect the description and the deltas: GH_PROMPT_DISABLED=1 GIT_TERMINAL_PROMPT=0 gh pr create --draft --fill --head $(git branch --show-current)
Write the PR description to a temp file with real newlines (e.g. pr-body.md ... EOF) and run pr-body.md to avoid \n-escaped markdown.
PR description (markdown) must be detailed prose covering the issue, the cause and effect on users, the root cause, the fix, and any tests or checks used to validate.