[make-pr] Add PR creation skill and workflow
This commit is contained in:
@@ -34,6 +34,36 @@ This document provides a reference for AI assistants working with YeetGeese. It
|
||||
|
||||
---
|
||||
|
||||
### `make-pr` — Pull Request Creation
|
||||
|
||||
**Purpose:** Create comprehensive pull requests from the current branch to a target branch (default: `develop`) with human-readable change overviews and testing strategies.
|
||||
|
||||
**Capabilities:**
|
||||
- Generating human-readable PR descriptions summarizing all changes
|
||||
- Listing testing strategies for each major change area
|
||||
- Validating changes before PR submission
|
||||
- Formatting PR descriptions with clear, organized sections
|
||||
- Identifying breaking changes and migration notes
|
||||
|
||||
**When to use:**
|
||||
- When ready to submit a pull request from your current branch
|
||||
- Before pushing code that requires peer review
|
||||
- To ensure all changes are properly documented and validated
|
||||
- When creating PRs for features, fixes, or refactoring
|
||||
|
||||
**Input required:**
|
||||
- Target branch (default: `develop`)
|
||||
- Optional custom PR title override
|
||||
- Optional specific testing requirements
|
||||
|
||||
**Example prompt:**
|
||||
```
|
||||
"Create a pull request from move_docs to develop. The changes include moving
|
||||
all AI documentation files into an 'AI Docs' folder with organized structure."
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Agent Types & Use Cases
|
||||
|
||||
### `code-gen` — Code Generation
|
||||
@@ -485,6 +515,7 @@ When requesting implementations:
|
||||
- `refactor-assistant`: Before code grows unmanageable
|
||||
- `test-generator`: After implementing critical logic
|
||||
- `design-patterns`: When architecture becomes unclear
|
||||
- `make-pr`: When ready to submit a pull request from current branch
|
||||
|
||||
**Always provide:**
|
||||
- File paths, node names, and Godot version context
|
||||
|
||||
Reference in New Issue
Block a user