task-flow-pr

Create and format GitHub pull requests using the repository's PR template.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/mahsanamin/ai_chest --skill task-flow-pr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: task-flow-pr
Source: https://github.com/mahsanamin/ai_chest/tree/main/SoftwareEngineering/Task_Flow/skills/task-flow-pr
Command: npx skills add https://github.com/mahsanamin/ai_chest --skill task-flow-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically creates and formats pull requests according to the repository's PR template, reducing manual steps and ensuring consistency.

Core Features & Use Cases

  • PR template adherence: fills in standard fields and checks for required sections.
  • Guarded approval flow: always asks for user review and confirmation before pushing or opening PRs.
  • Context-aware PR content: summarizes changes from the current branch to produce a ready-to-review PR body that aligns with project conventions.

Quick Start

Ask the skill to prepare a draft PR for the current branch and review the proposed title and body.

Frequently Asked Questions about task-flow-pr

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

FAQPage Schema
How do I automate GitHub pull request creation using a PR template?

Automating GitHub pull request creation involves reading the repository's PR template, filling in context from the current branch, and formatting the body to ensure compliance with project conventions before submission.

How does a guarded approval flow work for draft pull requests?

A guarded approval flow for draft pull requests guides users through reviewing the proposed PR content, selecting draft or ready status, and obtaining explicit user confirmation before pushing or creating the PR.

Can I generate a context-aware PR body from my current branch?

Yes, you can generate a context-aware PR body by summarizing code changes from the current branch to produce a ready-to-review pull request description that aligns with the repository's template and conventions.

Does the PR creation process require manual review before opening?

Yes, the PR creation process requires manual review; it always asks for explicit user approval and confirmation before pushing or opening the pull request, returning the PR URL only upon approval.

What is the best way to ensure consistency when formatting GitHub pull requests?

The best way to ensure consistency when formatting GitHub pull requests is to automatically fill in standard fields from the repository's PR template and check for required sections before creating the PR.