ryoppippi/dotfiles

Overview

This skill automates the complete pull request workflow from local changes to an opened PR. It creates a descriptive feature branch, crafts commits, pushes the branch to the remote, and opens a pull request with an appropriate, context-aware description. It reports progress at each step and requests clarification when needed.

How this skill works

The skill inspects the working tree, ensures you are not on main, and creates a new branch following semantic naming (feature/, fix/, chore/). It calls a commit-crafting helper to produce meaningful, atomic commit messages, pushes the branch to origin, and generates a PR body matched to the change complexity. Finally it runs gh pr create and opens the new PR in the browser, handling retries and shell alternatives when commands fail.

When to use it

• You have local changes ready and want them reviewed via PR.
• You need a branch created, commits crafted, and the branch pushed to remote.
• You want a clear, review-ready PR body tailored to the change scope.
• You prefer automating repetitive git + gh tasks but keep control of messages.
• You need guidance to follow branching and commit best practices.

Best practices

• Never work directly on main—always create a feature/fix/chore branch.
• Keep commits focused and atomic; call the commit crafter for clear messages.
• Match PR body verbosity to complexity: concise for small fixes, structured for large changes.
• Review the staged diff to exclude debug code or temp files before committing.
• Verify target branch (main or develop) and remote permissions before pushing.

Example use cases

• Create a PR for a single-file bug fix: branch, commit, push, open concise PR.
• Push a new feature across multiple files with a structured PR: summary, what changed, why, testing.
• Update documentation: branch and push with a short, 2–4 sentence PR body explaining the doc change.
• Perform a chore like dependency bump: branch, atomic commit, and PR noting scope and compatibility checks.