[PR Helper] Add Gitea API PR creation helper and make-pr skill
Validate Project / validate (push) Successful in 16s
Validate Project / validate (pull_request) Successful in 15s

This commit is contained in:
Andrew Yeet
2026-09-04 11:17:10 -07:00
parent 5edde52541
commit 957107ea49
4 changed files with 175 additions and 5 deletions
+9 -5
View File
@@ -1,6 +1,6 @@
{
"name": "make-pr",
"description": "Create pull requests from the current branch to develop with comprehensive change overview and testing strategies",
"description": "Create pull requests using Gitea API with comprehensive change overview and testing strategies",
"agent_type": "pr-creator",
"capabilities": {
"generate-pr-overview": "Human-readable summary of all changes including files modified, new features, fixes, and refactoring",
@@ -17,10 +17,9 @@
"input_required": [
"Target branch (default: 'develop')",
"Optional custom PR title override",
"Optional custom description overrides",
"Any specific testing requirements for the current change"
"Optional specific testing requirements for the current change"
],
"prompt_template": "Generate a pull request for changes from branch '{current_branch}' to '{target_branch}'.\\n\\nThe PR should include:\\n\\n1. Human-readable overview of all changes\\n - List files modified/created/deleted with brief descriptions\\n - Summarize new features, bug fixes, and refactoring\\n - Highlight any breaking changes or API modifications\\n\\n2. Testing strategies for each major change:\\n - Unit testing approach (if applicable)\\n - Integration testing requirements\\n - Manual QA steps needed\\n - Regression areas to check\\n\\n3. Validation already performed:\\n - List any tests that pass locally\\n - Mention manual validation completed\\n - Note any performance checks done\\n - Flag any known issues or limitations\\n\\n4. Clear context for reviewers:\\n - What problem does this solve?\\n - How does it relate to existing code?\\n - Any migration notes needed?",
"prompt_template": "Generate a pull request description from branch '{current_branch}' to '{target_branch}'.\n\nThe PR should include:\n\n1. Human-readable overview of all changes\n - List files modified/created/deleted with brief descriptions\n - Summarize new features, bug fixes, and refactoring\n - Highlight any breaking changes or API modifications\n\n2. Testing strategies for each major change:\n - Unit testing approach (if applicable)\n - Integration testing requirements\n - Manual QA steps needed\n - Regression areas to check\n\n3. Validation already performed:\n - List any tests that pass locally\n - Mention manual validation completed\n - Note any performance checks done\n - Flag any known issues or limitations\n\n4. Clear context for reviewers:\n - What problem does this solve?\n - How does it relate to existing code?\n - Any migration notes needed?",
"validation_steps": [
"Run git diff to analyze all changed files",
"Check that changes compile/validate in the project",
@@ -31,5 +30,10 @@
"pr_title": "Concise, descriptive title following conventional commits format when applicable",
"pr_body": "Structured with clear sections: Context, Changes, Testing Strategy, Validation Performed",
"reviewer_notes": "Optional notes highlighting key areas requiring attention"
},
"cli_commands": {
"create_pr": "curl -X POST \"${GITEA_HOST:-https://gitea.letteka.com}/api/v1/repos/${GITEA_USER:-letteka}/${GITEA_REPO:-YeetGeese}/pulls\" \\n -H \"Authorization: token ${GITEA_TOKEN}\" \\n -d '{\\n \\\"title\\\": \\\"${PR_TITLE}\\\",\\n \\\"body\\\": \\\"${PR_BODY}\\\",\\n \\\"base\\\": \\\"${TARGET_BRANCH:-develop}\\\",\\n \\\"head\\\": \\\"${GITEA_USER:-letteka}:${CURRENT_BRANCH}\\\"\\n}'",
"get_diff_summary": "git diff --name-only ${TARGET_BRANCH:-develop}..HEAD 2>/dev/null | wc -l || echo \"0\"",
"validate_git_status": "git status --short && git log -1 --oneline --quiet"
}
}
}