create-pr

Create pull requests from local git and GitHub CLI with task metadata.

84|5|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/fitlab-ai/agent-infra --skill create-pr-fitlab-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/fitlab-ai/agent-infra/tree/main/.agents/skills/create-pr
Command: npx skills add https://github.com/fitlab-ai/agent-infra --skill create-pr-fitlab-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of pull requests and synchronizes related task metadata, reducing manual steps and ensuring traceability across task contexts.

Core Features & Use Cases

  • Automated PR creation that targets the correct branch and attaches related task metadata.
  • Link PRs to the associated task (e.g., using task.md data such as issue_number) and ensure Closes #{issue-number} references.
  • Automatic PR body assembly from templates, with adherence to repository PR styles and assistant-generated content.

Quick Start

Create a PR from the current branch and attach it to the active task context.

Frequently Asked Questions about create-pr

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

FAQPage Schema
How do I automate pull request creation and sync task metadata in GitHub?

Automating pull request creation syncs task metadata by reading task.md files, determining target branches, assembling PR bodies from .github templates, and linking issues via Closes #{issue-number} references.

How does PR body assembly work with task-driven code changes?

PR body assembly automatically generates pull request descriptions by combining repository templates from .github with assistant-generated content, ensuring adherence to repository PR styles and linking associated task context.

Do I need the GitHub CLI and local git to automate PR creation?

Yes, automating PR creation relies on local git and GitHub CLI tooling to determine target branches, push changes, and link pull requests to corresponding issues found in .agents/workspace/active/{task-id}/task.md.

What is the best way to link a pull request to a corresponding GitHub issue?

Linking a pull request to a corresponding issue is handled automatically by reading issue_number data from task metadata and inserting Closes #{issue-number} references into the assembled PR body.

Can I use .agents rule files to manage task-driven software changes and PR workflows?

Yes, this approach uses .agents rule files and task.md metadata to drive PR workflows, automatically determining target branches and assembling pull request bodies to ensure traceability across task contexts.

Why does automated PR creation require .github repository templates?

Automated PR creation requires .github repository templates to assemble pull request bodies that adhere to specific repository PR styles, combining structured templates with dynamic task metadata for consistent code review.