pr-creation-workflow

Automate PR creation with configurable target branches, quality checks, and Jira tracking references.

4|4|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/darellchua2/opencode-config-template --skill pr-creation-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-creation-workflow
Source: https://github.com/darellchua2/opencode-config-template/tree/main/skills/pr-creation-workflow
Command: npx skills add https://github.com/darellchua2/opencode-config-template --skill pr-creation-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams spend substantial time creating PRs with inconsistent quality checks and scattered tracking references. This skill provides a reusable PR creation workflow that standardizes branch targeting, quality gates, and cross-system tracking.

Core Features & Use Cases

  • Configurable target branches: Determine the merge target from user input or repo config, avoiding hard-coded defaults.
  • Quality gate orchestration: Run lint, tests, type checks, builds, and documentation checks before PR creation.
  • Tracking integration: Detect Jira tickets or Git issues and automatically reference them in the PR body and commit messages.
  • Multi-target support: Create PRs against multiple branches or environments as part of a single workflow.
  • Rich PR descriptions with assets: Attach images or diagrams and embed links to tracking tickets.
  • Merge readiness: Update statuses post-merge (e.g., Jira) and ensure branch hygiene.

Quick Start

Use the pr-creation-workflow skill to create a PR for the current feature branch, linking to any Jira or Git issue detected in the repo.

Frequently Asked Questions about pr-creation-workflow

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

FAQPage Schema
How do I automate pull request creation with Jira tracking and quality checks?

Automate pull request creation by orchestrating configurable lint, test, and build quality gates, then automatically detect Jira tickets to embed as tracking references in the PR body and commit messages.

Can I configure target branches dynamically when automating PR creation?

Yes, dynamic target detection determines the merge target from user input or repository configuration, avoiding hard-coded defaults and enabling multi-target PR creation against multiple branches or environments.

How does a workflow handle Jira ticket linking in GitHub pull requests?

The workflow detects Jira tickets or Git issues within the repository and automatically generates rich PR descriptions with embedded links to the tracking tickets and attached assets like diagrams.

What is the best way to enforce quality gates before creating a pull request?

Enforce quality gates by orchestrating lint, tests, type checks, builds, and documentation checks before PR creation, ensuring merge readiness and maintaining branch hygiene across multi-platform integrations.

Does the automated PR workflow update Jira statuses post-merge?

Yes, the workflow updates tracking statuses in Jira post-merge to ensure merge readiness, while also maintaining branch hygiene across the integrated development environments.