Menü
Commit, push, and create a PR with summary and test checklist.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
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.
Check GitHub Actions status, diagnose failures from logs, fix, push, and loop until CI passes.
Read PR comments on the current branch and address each one through plan mode.
Explore the project and list setup steps needed to run it locally — dependencies, config, services, and manual actions.
Create .superset/config.json with setup and teardown scripts for Superset workspaces.
查看当前分支与主分支的差异，用简体中文给出一份面向非技术团队成员的高层次 PR 摘要。
| name | ready |
| description | Commit, push, and create a PR with summary and test checklist. |
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.
git rev-parse --abbrev-ref HEAD to get the current branch name.git remote show origin (or the configured remote) to determine the default branch.main, master), stop and tell the user:
"You are on the default branch. Create a feature branch first."
git status --porcelain to check for uncommitted changes (staged, unstaged, or untracked).git add -A to stage everything.git diff --cached and write a concise, meaningful commit message that describes why the changes were made, not just what changed.git commit with that message.git push -u origin HEAD
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.