Skip to content

fvadicamo/dev-agent-skills / plugins/github-workflow/skills/github-pr-creation

github-pr-creation

Verified

Creates GitHub Pull Requests with automated validation and task tracking. Use when user wants to create PR, open pull request, submit for review, or check if ready for PR. Analyzes commits, validates task completion, generates Conventional Commits title and description, suggests labels. NOTE - for merging existing PRs, use github-pr-merge instead.

FileKindSize
SKILL.mdskill md5.7 KB
references/pr_templates.mdmarkdown3.0 KB

references/pr_templates.md

View on GitHub
# PR templates

Select the template matching the PR type.

---

## Feature (feature/* -> develop)

**Title**: `feat(<scope>): <description>`

```markdown
## What
- [List of implemented features/components]
- [Main functionality highlights]

## Why
- [Business/operational impact]
- [Pain points resolved]

## Details
### Task X.Y: [Task title]
- [Implementation detail 1]
- [Implementation detail 2]
- **Requirements**: X, Y, Z

## Checklist
- [ ] Main feature implemented
- [ ] Tests written and passing
- [ ] Documentation updated
- [ ] Code review ready
```

---

## Release (develop -> main)

**Title**: `release: version X.Y with [main features]`

```markdown
## What
This release includes:
- [Feature set 1 - Task N]
- [Feature set 2 - Task M]

## Why
[Release motivation, milestone reached]

## Details
### Task N: [Feature name] (COMPLETE)
- **Task N.1**: [Description]
- **Task N.2**: [Description]
- **Requirements**: X, Y, Z

## Testing
- Coverage: XX%
- Integration tests: pass/fail

## Checklist
- [ ] All tasks completed
- [ ] No breaking changes (or documented)
- [ ] Migration guide prepared (if needed)
```

---

## Bugfix (fix/* -> develop)

**Title**: `fix(<scope>): <description>`

```markdown
## What
Fix for [problem description]

## Problem
[Bug description, how it manifests, impact]

## Solution
[Explanation of implemented solution]

## Testing
- [How the fix was tested]
- [Regression tests added]

## Checklist
- [ ] Bug resolved
- [ ] Regression tests added
- [ ] No side effects introduced
```

---

## Hotfix (hotfix/* -> main)

**Title**: `hotfix(<scope>): <critical fix>`

```markdown
## HOTFIX

### Issue
[Description of critical production issue]

### Root cause
[Identified cause]

### Fix
[Implemented solution]

### Impact
- Affected users: [estimate]
- Downtime: [if applicable]

### Rollback plan
[Rollback plan if needed]

## Checklist
- [ ] Fix tested in staging
- [ ] Approval for urgent deploy
- [ ] Post-deploy monitoring planned
```

---

## Refactoring (refactor/* -> develop)

**Title**: `refactor(<scope>): <description>`

```markdown
## What
Refactoring of [component/module]

## Why
- [Motivation: performance, maintainability, technical debt]

## Changes
- [Change 1]
- [Change 2]

## Impact
- **Functional**: None (behavior unchanged)
- **Performance**: [expected improvements]
- **Maintainability**: [benefits]

## Checklist
- [ ] Functional behavior unchanged
- [ ] Existing tests passing
- [ ] New tests added (if needed)
```

---

## Documentation (docs/*)

**Title**: `docs(<scope>): <description>`

```markdown
## What
Documentation update for [area]

## Changes
- [Document 1]: [change type]
- [Document 2]: [change type]

## Motivation
[Why this documentation is needed]
```

---

## CI/CD and infrastructure

**Title**: `ci(<scope>): <description>` or `chore(<scope>): <description>`

```markdown
## What
[Pipeline/infrastructure change]

## Changes
- [Change 1]
- [Change 2]

## Impact
- Build time: [variation]
- Deploy process: [variation]

## Testing
[How it was verified]
```
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