ftf-open-pr

Automates GitHub pull request creation for WordPress repositories using structured templates.

2|Updated Jun 14, 2020
One-click install
npx skills add https://github.com/jaballer/fivetwofive-cw --skill ftf-open-pr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ftf-open-pr
Source: https://github.com/jaballer/fivetwofive-cw/tree/main/.claude/skills/ftf-open-pr
Command: npx skills add https://github.com/jaballer/fivetwofive-cw --skill ftf-open-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of creating a GitHub pull request for the FiveTwoFive WordPress site, ensuring a structured and reviewable body is provided, saving time and reducing errors in the PR creation process.

Core Features & Use Cases

  • PR Automation: Automatically generates and opens a pull request based on specific user prompts or after successful commits.
  • Structured Body: Ensures the PR body is well-organized with sections for summary, decisions, test plan, and follow-ups.
  • Use Case: Use this Skill when you want to open a PR for a new feature or fix, and it will handle the PR creation process according to the standard Four-Section Template.

Quick Start

To open a PR, run the command: /ftf-open-pr

Frequently Asked Questions about ftf-open-pr

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

FAQPage Schema
How do I automate GitHub pull request creation for a WordPress repository?

Automate GitHub pull request creation by running a command that generates a PR with a structured body. This ensures a reviewable pull request with sections for summary, decisions, test plan, and follow-ups for the WordPress site.

Does this PR automation tool require a clean working branch and GitHub API access?

Yes, PR automation requires GitHub API access and a clean working branch to successfully generate and open a structured pull request for the WordPress repository.

What is the best way to ensure a structured PR body for code review?

The best way to ensure a structured PR body for code review is to use automation that enforces a four-section template covering summary, decisions, test plan, and follow-ups, reducing errors and saving time.

How do I open a pull request after committing changes to my site code?

Open a pull request after committing changes by triggering the automation command, which handles the GitHub API submission and formats the PR body automatically according to standard templates.

Can I use this automation to open a PR for both new features and fixes?

Yes, you can use this PR automation to open a pull request for either a new feature or a fix. It handles the GitHub PR creation process and applies a standard four-section template to maintain consistency.