Creating pull requests manually takes time and often results in incomplete descriptions. This skill automates PR creation with structured templates, ensuring consistent documentation and faster code reviews.
Baixar o ZIP da skill
Upload no Claude
Vá em Configurações → Capacidades → Skills → Upload skill
Ative e comece a usar
Testar
A utilizar "creating-pull-requests". Create a pull request titled 'Fix login timeout bug' with test checklist items: verify login works, check session expiry
Resultado esperado:
- ✅ Pull request created successfully
- 📋 Title: Fix login timeout bug
- 🔗 https://github.com/owner/repo/pull/123
- 📍 Target branch: main
- 📝 Test checklist included with 2 items
Auditoria de Segurança
SeguroPure prompt-based skill with no code execution beyond standard git and GitHub CLI operations. Uses only documented shell commands for branch checking, status review, and PR creation via gh CLI. No filesystem access beyond git repository, no environment variable reading, no network calls outside expected GitHub API endpoints.
Pontuação de qualidade
O Que Você Pode Construir
Streamline PR workflows
Quickly create well-documented pull requests with consistent templates and test checklists
Submit quality contributions
Generate professional PR descriptions that help maintainers review and merge contributions faster
Improve review documentation
Ensure every PR includes clear summaries and test plans for faster, more effective reviews
Tente Estes Prompts
Create a pull request with the title '[Brief description]' describing my changes
Create a pull request titled '[Feature name]' and include test checklist items: [Test item 1], [Test item 2]
Create a draft PR for my feature branch targeting the 'develop' branch with summary of changes
Create a pull request with title '[Your title]', base branch 'main', assign to me, add 'enhancement' label, and include this summary: [Your summary]
Melhores Práticas
- Run git status and review changes before creating a PR to ensure only intended modifications are included
- Use descriptive titles that summarize the change in under 60 characters for better visibility
- Fill in all test checklist items to help reviewers understand what verification is needed
Evitar
- Creating PRs without reviewing the diff first may include unintended changes
- Using vague titles like 'fix' or 'update' makes it harder to track changes in project history
- Skipping the test plan makes it difficult for reviewers to verify the implementation works correctly