
Commit Push Pr
- 2 installs
- 512 repo stars
- Updated February 11, 2026
- meleantonio/chernycode
Automates the git workflow to commit changes with Conventional Commits, push the branch, and open a pull request.
About
Runs pre-commit checks, stages and commits with Conventional Commits messages, pushes the branch, and creates a PR. A developer uses it to complete a feature or fix that is ready for review.
- Runs ruff format/check and pytest before committing
- Conventional Commits messages and automated push plus PR creation
Commit Push Pr by the numbers
- 2 all-time installs (skills.sh)
- Ranked #498 of 733 Git & Pull Requests skills by installs in the Skillselion catalog
- Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/meleantonio/chernycode --skill commit-push-prAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 2 |
|---|---|
| repo stars | ★ 512 |
| Last updated | February 11, 2026 |
| Repository | meleantonio/chernycode ↗ |
What it does
Automates the git workflow to commit changes with Conventional Commits, push the branch, and open a pull request.
Files
Commit, Push, and Create PR
Automate the git workflow for completing a feature or fix.
Pre-computed Context
Before proceeding, gather this information:
- Current branch:
!git branch --show-current - Git status:
!git status --short - Recent commits on this branch:
!git log --oneline -5 - Diff summary:
!git diff --stat
Workflow
1. Review Changes
- Check
git statusfor all modified/added files - Review the diff to understand what's being committed
- Ensure no sensitive files are staged (.env, credentials, etc.)
2. Run Pre-commit Checks
- Format code:
ruff format .(if Python files changed) - Lint code:
ruff check .(if Python files changed) - Run tests:
pytest(if tests exist)
3. Stage and Commit
- Stage relevant files:
git add <files> - Create a commit with Conventional Commits format:
feat:for new featuresfix:for bug fixesdocs:for documentationrefactor:for refactoringtest:for testschore:for maintenance- Write a clear, concise commit message focusing on "why"
4. Push to Remote
- Push the branch:
git push -u origin HEAD - If branch doesn't exist on remote, create it
5. Create Pull Request
- Use GitHub CLI:
gh pr create - Include:
- Clear title summarizing the change
- Description with summary and context
- Reference any related issues
- Add appropriate labels if applicable
Arguments
Pass a commit message or leave empty for auto-generated message based on changes.
Usage: /commit-push-pr [optional commit message]
Example: /commit-push-pr feat: add user authentication
Output
Return the PR URL when complete.