원클릭으로 Manus에서 모든 스킬 실행

시작하기

ready

스타1

포크0

업데이트2026년 3월 30일 06:03

Commit, push, and create a PR with summary and test checklist.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

GalvinGao

GalvinGao/skills

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Ready

When invoked, prepare the current branch for review by committing, pushing, and creating a pull request.

Follow these steps strictly and in order. Stop immediately if any step fails.

Step 1 — Validate branch

Run git rev-parse --abbrev-ref HEAD to get the current branch name.
Run git remote show origin (or the configured remote) to determine the default branch.
If the current branch is the default branch (e.g. main, master), stop and tell the user:

"You are on the default branch. Create a feature branch first."

Step 2 — Commit changes

Run git status --porcelain to check for uncommitted changes (staged, unstaged, or untracked).
If there are changes:
- Run git add -A to stage everything.
- Analyze the diff with git diff --cached and write a concise, meaningful commit message that describes why the changes were made, not just what changed.
- Run git commit with that message.
If there are no changes, skip this step (there must be at least one commit ahead of the default branch).

Step 3 — Push to remote

Push the branch to the remote:
```
git push -u origin HEAD
```
If the push fails, stop and report the error.

Step 4 — Create the Pull Request

Run git log --oneline origin/<default-branch>..HEAD to collect all commits being introduced.
Run git diff origin/<default-branch>...HEAD to understand the full scope of changes.
Compose a PR body with this structure:
```
## Summary
<2-5 bullet points describing what changed and why>

## Test checklist
- [ ] <actionable step to verify the change>
- [ ] <another step>
...
```
The Summary should be derived from the commits and diff. The Test checklist should list concrete, ordered steps someone can follow to manually verify this PR works correctly. Be specific — reference endpoints, pages, CLI commands, or test suites where applicable.
Create a draft PR using the gh CLI:
```
gh pr create --draft --title "<concise title>" --body "<body from above>"
```
Use a HEREDOC for the body to preserve formatting.
Output the resulting PR URL so the user can access it.

이 저장소의 다른 Skills

같은 저장소

baseline-ui

GalvinGao/skills

Validates animation durations, enforces typography scale, checks component accessibility, and prevents layout anti-patterns in Tailwind CSS projects. Use when building UI components, reviewing CSS utilities, styling React views, or enforcing design consistency.

2026-03-301

fix-ci

GalvinGao/skills

Check GitHub Actions status, diagnose failures from logs, fix, push, and loop until CI passes.

2026-03-301

fix-pr-comments

GalvinGao/skills

Read PR comments on the current branch and address each one through plan mode.

2026-03-301

preheat

GalvinGao/skills

Explore the project and list setup steps needed to run it locally — dependencies, config, services, and manual actions.

2026-03-301

setup-superset

GalvinGao/skills

Create .superset/config.json with setup and teardown scripts for Superset workspaces.

2026-03-301

summarize-pr

GalvinGao/skills

查看当前分支与主分支的差异，用简体中文给出一份面向非技术团队成员的高层次 PR 摘要。

2026-03-301

Ready

When invoked, prepare the current branch for review by committing, pushing, and creating a pull request.

Follow these steps strictly and in order. Stop immediately if any step fails.

Step 1 — Validate branch

Run git rev-parse --abbrev-ref HEAD to get the current branch name.

Run git remote show origin (or the configured remote) to determine the default branch.

If the current branch is the default branch (e.g. main, master), stop and tell the user:

"You are on the default branch. Create a feature branch first."

Step 2 — Commit changes

Run git status --porcelain to check for uncommitted changes (staged, unstaged, or untracked).

If there are changes:

Run git add -A to stage everything.
Analyze the diff with git diff --cached and write a concise, meaningful commit message that describes why the changes were made, not just what changed.
Run git commit with that message.

If there are no changes, skip this step (there must be at least one commit ahead of the default branch).

Step 3 — Push to remote

Push the branch to the remote:

git push -u origin HEAD

If the push fails, stop and report the error.

Step 4 — Create the Pull Request

Run git log --oneline origin/<default-branch>..HEAD to collect all commits being introduced.

Run git diff origin/<default-branch>...HEAD to understand the full scope of changes.

Compose a PR body with this structure:

## Summary
<2-5 bullet points describing what changed and why>

## Test checklist
- [ ] <actionable step to verify the change>
- [ ] <another step>
...

The Summary should be derived from the commits and diff. The Test checklist should list concrete, ordered steps someone can follow to manually verify this PR works correctly. Be specific — reference endpoints, pages, CLI commands, or test suites where applicable.

Create a draft PR using the gh CLI:

gh pr create --draft --title "<concise title>" --body "<body from above>"

Use a HEREDOC for the body to preserve formatting.

Output the resulting PR URL so the user can access it.

name	ready
description	Commit, push, and create a PR with summary and test checklist.