submit-pr

Create pull requests from feature branches with generated descriptions and CI checks.

12|4|Updated Feb 9, 2026

Search Tags:#automation #git #code-review #ci #pull-request #pre-submission

Ready to run

npx skills add https://github.com/andrewvaughan/agent-council --skill submit-pr

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: submit-pr
Source: https://github.com/andrewvaughan/agent-council/tree/main/canonical/skills/submit-pr
Command: npx skills add https://github.com/andrewvaughan/agent-council --skill submit-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines the process of turning feature branches into formal pull requests by automatically generating descriptive PR messages, running required checks, and coordinating with deployment workflows as needed.

Core Features & Use Cases

Auto-generates PR descriptions from commits to ensure clear context
Runs pre-submission quality checks and CI monitoring
Optionally activates the Deployment Council for production-impacting changes
Supports trunk-based development workflows and consistent PR templates

Quick Start

Create a PR from the current feature branch, let the workflow generate the description, run checks, and prompt for deployment decisions when needed.

Frequently Asked Questions about submit-pr

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

FAQPage Schema

How do I automatically generate a pull request description from my git commits?▼

Automating pull request creation generates descriptive PR messages directly from your feature branch commits. The workflow analyzes commit history to populate clear context and applies consistent PR templates for trunk-based development.

Can I run pre-submission quality checks before creating a pull request?▼

Yes, pre-submission quality checks run before finalizing pull request creation. The workflow executes required validation checks and monitors CI pipelines, using checkpoint prompts to require explicit user decisions before proceeding with the PR.

How do I automate CI monitoring during pull request creation on a feature branch?▼

Automating CI monitoring during pull request creation tracks your continuous integration pipelines after submission. The workflow coordinates checks on the feature branch and provides checkpoint prompts to ensure validation passes before deployment decisions.

Does this pull request automation work with trunk-based development workflows?▼

Yes, this pull request automation supports trunk-based development workflows. It streamlines turning short-lived feature branches into formal pull requests by applying consistent templates and pre-submission checks tailored for trunk-based environments.

What is the best way to prompt for deployment decisions after creating a pull request?▼

Prompting for deployment decisions after pull request creation uses checkpoint prompts to require explicit user confirmation. The workflow optionally activates deployment coordination for production-impacting changes, ensuring manual approval before proceeding.

Why do I need checkpoint prompts before proceeding with an automated pull request?▼

Checkpoint prompts are needed before proceeding with an automated pull request to require explicit user decisions. They prevent unintended deployments by pausing the workflow for manual confirmation whenever production-impacting changes or deployment actions are detected.