send-it

Push a feature branch and create a GitHub PR via gh CLI.

5|Updated Feb 17, 2026
One-click install
npx skills add https://github.com/Nathan13888/nice-skills --skill send-it
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: send-it
Source: https://github.com/Nathan13888/nice-skills/tree/main/skills/send-it
Command: npx skills add https://github.com/Nathan13888/nice-skills --skill send-it

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pushing feature branches and opening GitHub PRs can be error-prone and manual; this Skill automates the workflow to ensure consistency and speed.

Core Features & Use Cases

  • Preflight checks validate repository state and trunk context before operations.
  • Context gathering analyzes commits and diffs to draft a precise PR title and body.
  • PR drafting prompts for user confirmation, then pushes the branch and creates the PR via gh CLI.
  • Handles existing PRs with guidance on updates or creating a new PR.

Quick Start

Push your current feature branch and let the Skill draft a PR and open it for review after your confirmation.

Frequently Asked Questions about send-it

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate pushing a git branch and opening a pull request?

Automating git branch pushing and pull request creation involves running preflight checks, analyzing commits and diffs to draft a structured PR title and body, and executing the push and PR creation via gh CLI after user confirmation.

Do I need gh CLI installed to automate pull request creation from the command line?

Yes, you need gh CLI installed and authenticated, as the pull request creation workflow relies on Bash-based logic and gh CLI commands to push the feature branch and open the GitHub PR.

How does automated PR drafting analyze git commits to generate a PR description?

Automated PR drafting analyzes your local git commits and diffs to extract relevant context, using that data to craft a concise and structured PR title and body for the GitHub pull request.

What happens if a pull request already exists when automating branch push and PR creation?

If a pull request already exists for your feature branch, the workflow detects it and provides guidance on whether to update the existing PR or create a new one.

Can I review the PR title and body before the workflow pushes my feature branch?

Yes, the workflow requires user confirmation before pushing your feature branch and creating the PR, ensuring you can review the drafted title and body generated from your commits.

What's the best way to ensure safe pull request creation and branch context in a git workflow?

Safe pull request creation uses preflight checks to validate the repository state and trunk context before operations, ensuring proper branch management and preventing accidental pushes.