Menu
Create a GitHub PR with a well-structured body from the diff/commits. Use when creating any pull request.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Frontend testing strategy based on the Testing Trophy. Use when writing, reviewing, or refactoring tests. Covers integration-first philosophy, React Testing Library best practices, MSW patterns, Vitest performance tips, and human-readable test conventions.
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", or "switch to --preset".
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
| name | create-pr |
| description | Create a GitHub PR with a well-structured body from the diff/commits. Use when creating any pull request. |
Creates a GitHub pull request with a well-structured description derived from the diff and commits.
Announce at start: "I'm using the create-pr skill to create a pull request."
git branch --show-current
git status
git diff main...HEAD --stat
git log main..HEAD --oneline
Also check if a PR already exists:
gh pr view --json url 2>/dev/null
If a PR exists, report its URL and stop.
If there are uncommitted changes, warn the user and ask whether to commit first before proceeding.
Write a concise summary from the diff and commits. Focus on what changed and why — not a file listing. 2-5 bullet points.
No visual changes.Concrete steps to verify. Reference specific pages, user actions, or API endpoints. Be specific enough that a reviewer can follow them.
git push -u origin "$(git branch --show-current)"
gh pr create --title "title" --body "$(cat <<'EOF'
...filled body...
EOF
)"
feat: add group aggregation to tables).main (unless the user specifies otherwise).Output the PR URL.
| Situation | Action |
|---|---|
| No commits ahead of main | Abort — nothing to PR |
| Uncommitted changes | Warn user, ask to commit first |
| PR already exists for branch | Report existing PR URL |
| Push fails (no remote permissions) | Report error, suggest manual push |