Menu
Creates a git commit and pushes to remote. Use -a to amend. Optionally accepts a commit message.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Use this skill for code review and PR review tasks. Covers review methodology, what to flag, what to skip, and output structure.
Use this skill after completing code changes to review for reuse, quality, and efficiency. Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality.
Use this skill for any coding task that involves working with repositories, writing code, creating branches, or opening pull requests. Covers the full development workflow from cloning to PR.
Use this skill to write and run SQL queries, pull data, build metrics, or answer analytical questions. Always use this skill when you need to query data.
You are a data triager that answers data questions by routing them across a network of skills and agents. These questions may involve pulling data from a Snowflake warehouse, computing metrics, locating relevant tables or fields, diagnosing a metric change, or performing exploratory analysis. Your job is to determine how to answer a question and which skills and subagents to invoke.
Use this skill for any data or analytics task — querying databases, analyzing metrics, exploring data warehouses, processing datasets, or creating visualizations.
| name | commit-push-pr |
| description | Creates a git commit and pushes to remote. Use -a to amend. Optionally accepts a commit message. |
Create a git commit with all modified code and push to the remote repository.
Run git status to see what files have changed. Stage the relevant changes:
git add <file> for specific files or git add -A if all changes should be committedIf amending:
git commit --amend -m "<message>"git commit --amend --no-edit to keep the previous messageOtherwise:
git diff --cached to see what's staged, then draft a concise commit messagePush to the remote. If amending, use git push --force-with-lease. If no upstream exists, add -u origin <branch-name>. Both flags can be combined if needed.
Check if a PR already exists for this branch: gh pr view --json url 2>/dev/null
gh pr create --draft --title "<title>" --body "<body>"--force unless explicitly requested--no-verify) unless explicitly requestedgh repo fork --remote=true), then push to the fork and open a PR against the upstream repo