mt-submit-pr

Create or update GitHub pull requests with branch validation and diff analysis.

Updated May 15, 2026
One-click install
npx skills add https://github.com/t-miura-024/tools --skill mt-submit-pr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mt-submit-pr
Source: https://github.com/t-miura-024/tools/tree/main/chezmoi/dot_config/opencode/skills/mt-submit-pr
Command: npx skills add https://github.com/t-miura-024/tools --skill mt-submit-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the process of creating or updating pull requests by coordinating branch checks, change analysis, background collection, and GitHub PR operations.

Core Features & Use Cases

  • Branch Validation and Diff Analysis: Verifies feature or hotfix branches and uses related branch comparison workflows to understand changes before PR creation.
  • PR Generation and Updates: Creates draft pull requests or updates existing ones with structured Japanese descriptions using GitHub CLI.
  • Context-Aware Documentation: Collects background information from Notion or user input and incorporates it into PR summaries.
  • Use Case: Use this Skill when preparing a feature branch for review and needing a consistent PR description based on the actual code changes.

Quick Start

Ask the skill to create a pull request from the current feature branch using the repository changes.

Frequently Asked Questions about mt-submit-pr

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

FAQPage Schema
How do I create a GitHub pull request with an automated description from my feature branch?

Creating a GitHub pull request from a feature branch is automated by validating the branch, analyzing the diff, and generating a structured PR description using GitHub CLI. This Skill coordinates branch checks and code change analysis to build the PR content automatically.

What's the best way to update an existing draft pull request after merging changes from the main branch?

Updating an existing draft pull request after a merge involves synchronizing your feature branch and collecting the new diff. This Skill performs merge synchronization, validates the updated branch, and revises the PR description to reflect the latest code changes.

Do I need the GitHub CLI installed to automate pull request creation and branch validation?

Yes, the GitHub CLI is required to automate pull request creation and branch validation. This Skill depends on gh CLI integration to execute the structured workflow for branch checks, diff collection, and draft PR management.

Can I include external background context from Notion in my automated pull request summary?

Yes, you can include external background context from Notion in your pull request summary. This Skill collects background information from Notion or direct user input and incorporates it contextually into the generated PR descriptions.

Does this pull request automation tool handle both feature branches and hotfix branches?

Yes, this pull request automation handles both feature branches and hotfix branches. It verifies branch types during validation and applies the appropriate diff analysis and PR generation workflows before opening a draft pull request.

Why are my pull request descriptions generated in Japanese instead of English?

Pull request descriptions are generated in Japanese because this Skill creates structured Japanese summaries by default. It analyzes your code changes and formats the background context into a Japanese PR description using the GitHub CLI.