Menü
Automates the process of summarizing changes into a concise conventional commit and creating a GitHub Pull Request. Always uses a feature branch to ensure PR creation.
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.
Pressure-test an assumption, architecture decision, estimate, or inherited constraint. Use when the user asks to challenge a belief, play devil's advocate, test reasoning, or find a simpler alternative.
Explain a code location, component, command, or user-facing system flow. Use when the user asks what code does, why it exists, how a feature works, or wants a trace of entry points, branches, dependencies, and side effects.
Prepare difficult technical or delivery news for a client, stakeholder, or team. Use for delays, incidents, security findings, cost changes, failed approaches, or other conversations where clarity and trust matter.
Plan and work through project, client, vendor, or team offboarding. Use for handovers, access removal, ownership transfer, documentation, credential rotation, data cleanup, and knowledge-transfer checklists.
Discover how a codebase already handles a concern before extending it. Use when asked how the repository does something, where a pattern lives, whether implementations are consistent, or what convention new work should follow.
Help the user think through a confusing problem or decision by asking focused questions and reflecting their reasoning. Use when they want to think out loud, untangle a problem, or find the question beneath the question.
Basierend auf der SOC-Berufsklassifikation
| name | github-pr |
| description | Automates the process of summarizing changes into a concise conventional commit and creating a GitHub Pull Request. Always uses a feature branch to ensure PR creation. |
This skill automates the transition from local changes to a GitHub Pull Request by ensuring you're on a dedicated feature branch.
git diff and provide a concise summary of the changes.feat: add medication tracking, fix: resolve N+1 query in dashboard).main, create a new branch based on the commit subject (e.g., feat/add-med-tracking): git checkout -b <branch-name>git add .git commit -m "<message>"git push origin HEADgh CLI to create a pull request:
gh pr create --title "<commit-subject>" --body "<commit-body>"
feat/, fix/, chore/, or refactor/ prefixes for branch names.