com um clique
commit-push-pr
Commit, push, and open a PR
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ê.
Menu
Commit, push, and open a PR
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
| name | commit-push-pr |
| description | Commit, push, and open a PR |
| disable-model-invocation | true |
| allowed-tools | ["Bash(git checkout --branch:*)","Bash(git add:*)","Bash(git status:*)","Bash(git push:*)","Bash(git commit:*)","Bash(gh pr create:*)"] |
git statusgit diff HEADgit branch --show-currentgit log --oneline -10If the codebase follows conventional commits (visible in recent commits above), the commit type must follow these rules:
Based on the above changes:
gh pr createRebase the current branch with smart conflict resolution.
Manage, organize, sort, rename, dedupe, or archive files on disk. Use when reshaping a directory tree, batch-renaming, deduplicating, sorting media by date or location, mounting or extracting disk images, or cleaning up a folder. Skip for git operations and code edits.
Guide for creating Dagger modules, toolchains, and CI pipelines using the Go SDK. Use this skill whenever the user wants to create or modify a Dagger module, build a toolchain, write Dagger Functions in Go, or set up CI/CD with Dagger. Also trigger when you see dagger.json, the dagger CLI, imports from dagger, or references to the `dag` client.
Reference and guidance for writing Taskfiles (Taskfile.yaml) and using the `task` / go-task CLI (https://taskfile.dev/). Trigger when the user edits or creates Taskfile.yaml files, runs or troubleshoots the `task` CLI, or asks about Task or `go-task`. SKIP when the user is discussing generic to-do lists, Celery/Airflow/Luigi tasks, Claude Code's own TaskCreate/TaskList tools, or macOS Reminders.
Retrospective on the current session's friction (broken tool calls, repeated prompts, wasted effort), with proposed fixes.
Review code and prose changes against the plan they implemented.