/pr-create

Spawn the workflow-specialist agent using:

Task(cms-cultivator:workflow-specialist:workflow-specialist,
     prompt="Create a comprehensive pull request for the user's changes. Analyze git changes, detect CMS-specific modifications (Drupal/WordPress), orchestrate quality checks by spawning specialists in parallel as needed, generate PR description following project template, and create the pull request using gh CLI. Ticket number: [use argument if provided]")

The workflow specialist will:

1. Analyze git changes - Review commits, diffs, and modified files since branching from main
2. Detect CMS-specific changes:
   • Drupal: Config changes, module updates, update hooks, services, routes, permissions, entity definitions
   • WordPress: Theme changes, Gutenberg blocks, ACF fields, custom post types, shortcodes
3. Orchestrate quality checks - Spawn specialists in parallel as needed:
   • testing-specialist - If tests exist or are needed
   • security-specialist - If security-critical code detected
   • accessibility-specialist - If UI/frontend changes detected
4. Generate PR description - Following your project's template with:
   • User story and description
   • Acceptance criteria extracted from code changes
   • Deployment notes (dependencies, config imports, database updates)
   • Steps to validate with specific admin paths
5. Present PR description for your approval or edits - Review and modify before creation
6. Verify prerequisites - Check gh CLI installation, authentication, branch status
7. Create pull request - Execute gh pr create with approved description
8. Return PR URL - Provide link to created pull request

Quick Start

# 1. Commit and push your changes
git add .
git commit -m "Your commit message"
git push -u origin feature-branch

# 2. Run this command
/pr-create

# Or with ticket number:
/pr-create PROJ-123

How It Works

This command spawns the workflow-specialist agent, which orchestrates the entire PR creation workflow. The workflow specialist uses the commit-message-generator skill and delegates to other specialists for comprehensive quality checks.

Agent Orchestration

The workflow specialist will intelligently spawn other agents in parallel based on your changes:

• Security-critical code? → security-specialist checks for OWASP vulnerabilities, input validation, SQL injection risks
• UI/frontend changes? → accessibility-specialist validates WCAG compliance, semantic HTML, ARIA usage
• New features or modified code? → testing-specialist analyzes test coverage and generates test plans

All specialist findings are compiled into a unified PR description with prioritized action items.

PR Description Template

The workflow specialist generates descriptions following this structure:

## Description
Teamwork Ticket(s): [PROJ-123](link)
- [ ] Was AI used in this pull request?

> As a developer, I need to...

[Comprehensive summary of changes and goals]

## Acceptance Criteria
* Extracted from code changes
* Specific, testable criteria
* Admin paths and validation steps

## Assumptions
* Known issues or limitations
* Environment-specific notes

## Steps to Validate
1. Direct links to test sites
2. Explicit testing instructions
3. Expected outcomes

## Affected URL
[link_to_multidev_or_test_site]

## Deploy Notes
[Dependencies, config imports, database updates, cache clearing]

Prerequisites

The workflow specialist verifies:

• ✅ GitHub CLI (gh) is installed and authenticated
• ✅ Current branch is NOT main/master
• ✅ Commits exist to create PR for
• ✅ Branch is pushed to remote (or pushes it for you)

Ticket Number Handling

Provide ticket number as argument:

/pr-create PROJ-123

Or let the workflow specialist extract it from:

• Branch name: feature/PROJ-123-description
• Commit messages: Contains PROJ-123
• Manual prompt: Agent will ask if not found

Error Handling

The workflow specialist handles:

• gh not installed - Provides installation instructions
• Not authenticated - Guides through gh auth login
• On main/master - Warns that a feature branch is needed
• No commits - Explains nothing to create PR for
• Branch not pushed - Automatically pushes with tracking
• PR already exists - Shows existing PR URL

Optional PR Options

The workflow specialist can add:

• Labels: --label bug,enhancement
• Reviewers: --reviewer username1,username2
• Assignees: --assignee username
• Draft mode: --draft
• Project: --project "Project Name"

Just mention these in your request:

/pr-create PROJ-123 - mark as draft and assign to me

CMS-Specific Detection

Drupal Projects

The workflow specialist detects and documents:

• Config changes: config/sync/*.yml → Config import required
• Update hooks: hook_update_N() → Database updates needed
• Module changes: modules/custom/ → Module dependencies
• Services: *.services.yml → Service definitions
• Routes: *.routing.yml → New endpoints
• Permissions: *.permissions.yml → Permission changes
• Entities: Field definitions, view modes, form displays

WordPress Projects

The workflow specialist detects and documents:

• Theme changes: Template files, functions.php
• Gutenberg blocks: blocks/ directories
• ACF fields: acf-json/ exports
• Custom post types: CPT registrations
• Shortcodes: New shortcode implementations
• Must-use plugins: mu-plugins/ changes

Related Commands

• /pr-commit-msg - Generate commit message first
• /pr-review self - Self-review before creating PR
• /pr-release - Create release PR with changelog

Agent Used

workflow-specialist - Orchestrates PR creation with parallel specialist delegation for comprehensive quality checks.

What Makes This Different

Before (manual PR creation):

• Write PR description yourself
• Manually identify deployment steps
• Miss security/accessibility concerns
• No automated quality checks

With workflow-specialist:

• ✅ Automated PR description generation
• ✅ CMS-specific deployment notes
• ✅ Parallel quality checks (security, testing, accessibility)
• ✅ Comprehensive acceptance criteria
• ✅ Direct validation links
• ✅ Compiled specialist findings