letteka/YeetGeese
1
0
Fork 0
Code Issues 8 Pull Requests Actions Packages Projects Releases Wiki Activity

Develop #15

Merged
letteka merged 13 commits from develop into main 2026-09-04 11:52:46 -07:00
Conversation 0 Commits 13 Files Changed 11
+14 -19
1 changed files with 14 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Showing only changes of commit 8f79eb1aae - Show all commits
AI Docs/05-SKILLS-REFERENCE.md
+14 -19
View File
@@ -34,16 +34,16 @@ This document provides a reference for AI assistants working with YeetGeese. It
--- ---
### `make-pr` — Pull Request Creation ### `make-pr` — Pull Request Creation (Gitea Web UI)
**Purpose:** Create comprehensive pull requests from the current branch to a target branch (default: `develop`) with human-readable change overviews and testing strategies. **Purpose:** On Gitea, pull requests are created directly via the web interface at:
`https://gitea.letteka.com/letteka/YeetGeese/pulls/new/move_docs`
**Capabilities:** **How to use on Gitea:**
- Generating human-readable PR descriptions summarizing all changes 1. Push changes to a branch (e.g., `move_docs`)
- Listing testing strategies for each major change area 2. Visit the URL above or navigate via Gitea web UI
- Validating changes before PR submission 3. Create PR with descriptive title and body
- Formatting PR descriptions with clear, organized sections 4. Include testing strategies and validation status in description
- Identifying breaking changes and migration notes
**When to use:** **When to use:**
- When ready to submit a pull request from your current branch - When ready to submit a pull request from your current branch
@@ -51,16 +51,12 @@ This document provides a reference for AI assistants working with YeetGeese. It
- To ensure all changes are properly documented and validated - To ensure all changes are properly documented and validated
- When creating PRs for features, fixes, or refactoring - When creating PRs for features, fixes, or refactoring
**Input required:** **Best practices for Gitea PRs:**
- Target branch (default: `develop`) - Use descriptive titles following conventional commits format
- Optional custom PR title override - Include file-by-file change summary in PR body
- Optional specific testing requirements - List testing strategies: unit tests, integration tests, manual QA
- Mention any validation already performed locally
**Example prompt:** - Flag known issues or limitations clearly
```
"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."
```
--- ---
@@ -515,7 +511,6 @@ When requesting implementations:
- `refactor-assistant`: Before code grows unmanageable - `refactor-assistant`: Before code grows unmanageable
- `test-generator`: After implementing critical logic - `test-generator`: After implementing critical logic
- `design-patterns`: When architecture becomes unclear - `design-patterns`: When architecture becomes unclear
- `make-pr`: When ready to submit a pull request from current branch
**Always provide:** **Always provide:**
- File paths, node names, and Godot version context - File paths, node names, and Godot version context