dots-workstation-pr-fallback

Generate structured pull request bodies with YAML and Markdown placeholders.

2|3|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/ulises-jeremias/agentic-workstation --skill dots-workstation-pr-fallback
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dots-workstation-pr-fallback
Source: https://github.com/ulises-jeremias/agentic-workstation/tree/main/home/dot_local/share/agentic-workstation/skills/dots-workstation-pr-fallback
Command: npx skills add https://github.com/ulises-jeremias/agentic-workstation --skill dots-workstation-pr-fallback

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Provides a default structure for pull request (PR) bodies when no custom template is available in the repository, streamlining PR creation for consistency and efficiency.

Core Features & Use Cases

  • Default PR Structure: Automatically fills in a structured PR body based on a predefined template when no repository-specific template is present.
  • Integration with Handshake and Workflow Skills: Pair this Skill with dots-workstation-output-handshake and github-cli-workflow for a seamless PR creation experience.
  • GitLab Support: Offers a similar structured approach for GitLab merge requests for consistent workflow practices.
  • Use Case: If you are frequently creating PRs without a predefined template, this Skill will automatically format the PR body for you, ensuring a standardized and comprehensive description.

Quick Start

Use the 'dots-workstation-pr-fallback' skill to create a new pull request with the default PR body structure.

Frequently Asked Questions about dots-workstation-pr-fallback

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

FAQPage Schema
How do I create a structured pull request body when my repository has no custom template?

To create a structured pull request body without a custom template, use a fallback PR generator. It automatically constructs a comprehensive PR outline using YAML and Markdown with placeholders for manual completion.

Does the fallback pull request template work with both GitHub and GitLab?

Yes, the fallback PR template works with both GitHub and GitLab. It provides a compatible structured formatting approach for pull requests and merge requests to maintain consistent workflow practices.

What is the best way to ensure consistent PR descriptions across multiple repositories?

The best way to ensure consistent PR descriptions is to apply a default PR structure. A fallback template automatically fills in a predefined format when no repository-specific template is present.

How do I format a merge request outline for manual completion in Markdown?

You format a merge request outline by generating a structured PR body with YAML and Markdown. This constructs a comprehensive outline with specific placeholders designed for manual completion.

Can I integrate a default PR body generator with existing GitHub CLI workflows?

Yes, you can integrate a default PR body generator with existing workflows. Pairing this Skill with handshake and GitHub CLI workflow skills creates a seamless pull request creation experience.

When should I avoid using a default pull request template fallback?

You should avoid using a default pull request template fallback when your repository already contains a custom PR template. It is designed specifically to provide default formatting only when no repository-specific template is present.