Run any Skill in Manus with one click

pr

Stars181

Forks22

UpdatedApril 10, 2026 at 16:25

Use when the user wants to open a pull request or finish a branch handoff. Read the PR template, inspect changes vs main, run the release skill first if the branch name looks like a version, validate the branch with the shared repo checks, open a draft PR targeting main, and return the preview deployment URL when one applies.

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

zacharyfmarion

zacharyfmarion/openscad-studio

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	pr
description	Use when the user wants to open a pull request or finish a branch handoff. Read the PR template, inspect changes vs main, run the release skill first if the branch name looks like a version, validate the branch with the shared repo checks, open a draft PR targeting main, and return the preview deployment URL when one applies.

Open Pull Request

Read .github/PULL_REQUEST_TEMPLATE.md and understand its required sections.
Inspect what has changed on this branch vs main. If there are unrelated changes, stop and ask the user what to do.
If the branch name looks like a release branch or versioned release workflow, run the release skill first before continuing.
Choose the right validation scopes for the changed files and run them through scripts/validate-changes.sh.
Prefer bash scripts/validate-changes.sh --scope baseline for normal TS or workflow changes. Add scopes when needed:
- --scope formatter for formatter behavior changes
- --scope rust for apps/ui/src-tauri or other desktop-only changes
- --scope e2e-web for materially changed user-facing web flows
If formatting fixes are still needed before validation, run pnpm format intentionally first, then rerun the validation helper in check mode. Do not rely on the helper to mutate files unless you explicitly choose --fix.
Draft a PR title and body that follow the template exactly, filling each section from the actual branch changes, validations run, validations skipped, and tests added.
Open or update a draft PR against main:
- Create with gh pr create --draft --base main when no PR exists for the branch.
- Update the existing PR body when one already exists.
After the PR exists, wait for the Deploy PR Preview workflow when the change is web-relevant.
Return:

the full PR URL
the preview URL when one applies
any explicit follow-up if the preview deploy or sticky comment failed

Preview Expectations

Web-relevant PRs should publish to https://pr-<number>.openscad-studio.pages.dev
Docs-only and desktop-only PRs may skip preview deployment
If Cloudflare deploy succeeds but the sticky comment fails, report that separately instead of pretending the preview is unavailable

More from this repository

same repository

create-feature

zacharyfmarion/openscad-studio

Use when the user asks to take a feature or bug fix from prompt to implementation, especially prompts like "/create a new feature", "build this feature end-to-end", "take this from plan to PR", or "own this change through validation and handoff". This skill is for repo-local delivery workflows that must create and maintain implementation plans, choose appropriate tests, run deterministic validation, open a draft PR against main, and return the preview deployment URL when one is available.

2026-03-29181

adapt

zacharyfmarion/openscad-studio

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

2026-03-18181

animate

zacharyfmarion/openscad-studio

Review a feature and enhance it with purposeful animations, micro-interactions, and motion effects that improve usability and delight.

2026-03-18181

arrange

zacharyfmarion/openscad-studio

Improve layout, spacing, and visual rhythm. Fixes monotonous grids, inconsistent spacing, and weak visual hierarchy to create intentional compositions.

2026-03-18181

audit

zacharyfmarion/openscad-studio

Perform comprehensive audit of interface quality across accessibility, performance, theming, and responsive design. Generates detailed report of issues with severity ratings and recommendations.

2026-03-18181

bolder

zacharyfmarion/openscad-studio

Amplify safe or boring designs to make them more visually interesting and stimulating. Increases impact while maintaining usability.

2026-03-18181

name	pr
description	Use when the user wants to open a pull request or finish a branch handoff. Read the PR template, inspect changes vs main, run the release skill first if the branch name looks like a version, validate the branch with the shared repo checks, open a draft PR targeting main, and return the preview deployment URL when one applies.

Open Pull Request

Read .github/PULL_REQUEST_TEMPLATE.md and understand its required sections.
Inspect what has changed on this branch vs main. If there are unrelated changes, stop and ask the user what to do.
If the branch name looks like a release branch or versioned release workflow, run the release skill first before continuing.
Choose the right validation scopes for the changed files and run them through scripts/validate-changes.sh.
Prefer bash scripts/validate-changes.sh --scope baseline for normal TS or workflow changes. Add scopes when needed:
- --scope formatter for formatter behavior changes
- --scope rust for apps/ui/src-tauri or other desktop-only changes
- --scope e2e-web for materially changed user-facing web flows
If formatting fixes are still needed before validation, run pnpm format intentionally first, then rerun the validation helper in check mode. Do not rely on the helper to mutate files unless you explicitly choose --fix.
Draft a PR title and body that follow the template exactly, filling each section from the actual branch changes, validations run, validations skipped, and tests added.
Open or update a draft PR against main:
- Create with gh pr create --draft --base main when no PR exists for the branch.
- Update the existing PR body when one already exists.
After the PR exists, wait for the Deploy PR Preview workflow when the change is web-relevant.
Return:

the full PR URL
the preview URL when one applies
any explicit follow-up if the preview deploy or sticky comment failed

Preview Expectations

Web-relevant PRs should publish to https://pr-<number>.openscad-studio.pages.dev
Docs-only and desktop-only PRs may skip preview deployment
If Cloudflare deploy succeeds but the sticky comment fails, report that separately instead of pretending the preview is unavailable