[make-pr] Add PR creation skill and workflow

2026-09-04 09:44:09 -07:00
parent c36afc75e5
commit ff9ca19d05
3 changed files with 320 additions and 0 deletions
@@ -0,0 +1,35 @@
+{
+  "name": "make-pr",
+  "description": "Create pull requests from the current branch to develop 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",
+    "list-testing-strategies": "Suggest comprehensive testing approaches for each change (unit tests, integration tests, manual QA)",
+    "validate-changes": "Perform git diff analysis to ensure validation is ready before PR creation",
+    "format-pr-description": "Structure PR description with clear sections for context, changes, testing, and validation"
+  },
+  "when_to_use": [
+    "When you are ready to create a pull request from your current branch to develop",
+    "Before pushing code that requires peer review",
+    "When implementing features or fixes that need documentation in the PR",
+    "To ensure all changes are properly documented and validated before review"
+  ],
+  "input_required": [
+    "Target branch (default: 'develop')",
+    "Optional custom PR title override",
+    "Optional custom description overrides",
+    "Any 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?",
+  "validation_steps": [
+    "Run git diff to analyze all changed files",
+    "Check that changes compile/validate in the project",
+    "Review for obvious bugs or unintended side effects",
+    "Ensure PR description is clear and complete"
+  ],
+  "output_format": {
+    "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"
+  }
+}