Stage, commit, push, and open a GitHub pull request via gh.
npx skills add https://github.com/segersniels/dotfiles --skill yeet
Please help me install this Agent Skill. Skill: yeet Source: https://github.com/segersniels/dotfiles/tree/main/.codex/skills/yeet Command: npx skills add https://github.com/segersniels/dotfiles --skill yeet
This skill enables end-to-end GitHub workflow automation to stage changes, commit with a concise message, push to a feature branch, and open a pull request using the GitHub CLI, reducing manual steps and context switching.
Stage all changes, commit with a concise message, push to a branch named codex/{description}, and open a pull request using gh.
High-intent search queries and answers about installing and using this skill.
You can automate the entire git workflow by running a single command that stages local changes, commits them, pushes to a feature branch, and opens a pull request via the GitHub CLI. This eliminates manual context switching between git commands.
Yes, the GitHub CLI (gh) must be installed and authenticated on your machine before automating your git commit and pull request workflow. The skill relies on gh to push branches and open pull requests seamlessly.
The workflow enforces a specific branch naming convention of codex/{description} when pushing changes to GitHub. Pull request titles are also automatically formatted as [codex] {description} for consistent tracking.
The best way to streamline a git workflow is using an end-to-end automation tool that stages, commits, pushes, and opens a PR in one sequence. This reduces manual steps and ensures consistent commit messages and branch naming across your repository.
The automation generates a concise, terse commit message for your git push and pull request flow rather than prompting for a custom one. This ensures uniformity across commits while moving your code directly to a GitHub feature branch.
Your automated pull request workflow requires the codex/{description} branch naming convention to maintain strict organizational consistency. This standardized prefix ensures all automated branches and PR titles are easily identifiable within your GitHub repository.
dyoshikawaAnalyzes GitHub pull requests for code quality, security vulnerabilities, and CI/CD workflow status.
nikhilsitaramMerge reviewed GitHub pull requests and clean up branches and worktrees.
shifuminCommit staged Git changes with Conventional Commits and push to remote.
mhattingpeteStage, commit, and push code changes with conventional commit messages.
