Skip to content

Unique-AG/ai / .claude/skills/pr-create

pr-create

Verified

Proactively draft and create pull requests by inferring title, refs, and body from git context, then confirm and open via gh CLI.

FileKindSize
SKILL.mdskill md5.4 KB
assets/pr-description.templateother1.3 KB

assets/pr-description.template

View on GitHub
# PR Description Template

## Title
<!-- Use semantic commit format: <type>(<scope>): <subject> -->
<!-- type: feat, fix, chore, ci, deploy, docs, improvement, refactor, test -->
<!-- scope: optional, describes the area affected (e.g., auth, api, ui) -->
<!-- subject: imperative mood, concise description -->

`feat(example): add new feature description`

## Refs
<!-- Link to Jira issue or ticket tracking system -->
<!-- Format: PROJ-123 or https://jira.example.com/browse/PROJ-123 -->
<!-- If none, ask, or remove ## Refs directly -->

PROJ-123

## Summary
<!-- One sentence: what changed? Describe the change concisely from a user/business perspective. -->

This PR adds...

## Testing
<!-- How can a reviewer verify this change works? Be specific and actionable. -->
<!-- Include: manual test steps, how to run automated tests, what to look for -->

Run `npm test` to verify all tests pass.

Manual verification:
1. Step 1 to test manually
2. Step 2 to verify behavior
3. Expected result

## Breaking Changes
<!-- Only include if there are breaking changes or migrations needed. -->
<!-- Delete this section if not applicable. -->

BREAKING CHANGE: [Describe what breaks and how to migrate, if nothing, remove]

---

**Copy & paste the sections above into your Git hosting platform (GitHub, GitLab, etc.)**
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall