From magic-powers
Use when creating pull requests - PR structure, description templates, review checklist, merge strategies, branch naming
npx claudepluginhub kienbui1995/magic-powers --plugin magic-powersThis skill uses the workspace's default tool permissions.
Good PRs are small, well-described, and easy to review. A PR is a communication tool, not just a code delivery mechanism.
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
Good PRs are small, well-described, and easy to review. A PR is a communication tool, not just a code delivery mechanism.
| Size | Lines Changed | Review Time | Quality |
|---|---|---|---|
| ✅ Small | <200 | 15 min | Best reviews |
| ⚠️ Medium | 200-400 | 30 min | Acceptable |
| ❌ Large | >400 | 60+ min | Rubber-stamp risk |
If PR is too large: split into stacked PRs (infra → logic → UI).
## What
Brief description of the change.
## Why
Link to issue/ticket. Context on why this approach.
## How
Key implementation decisions. What reviewers should focus on.
## Testing
- [ ] Unit tests added/updated
- [ ] Manual testing done
- [ ] Edge cases considered
## Screenshots
(if UI change)
feature/TICKET-123-add-user-auth
fix/TICKET-456-null-pointer-login
chore/update-dependencies
docs/api-authentication-guide
| Strategy | History | Use When |
|---|---|---|
| Squash merge | Clean, 1 commit per PR | Default for most teams |
| Merge commit | Preserves all commits | Need full history |
| Rebase | Linear history | Small teams, clean commits |
| Pattern | Fix |
|---|---|
| "WIP" PRs open for days | Use draft PRs, keep them short-lived |
| No description | Require PR template |
| Mixing refactor + feature | Separate PRs |
| Approving without reading | Use review checklist |