Automatically creates comprehensive pull requests to the dev branch when user indicates their feature/fix is complete and ready for review. Use when user mentions creating PR, submitting for review, or indicates work is done. Examples - "create a PR", "ready for review", "open a pull request", "submit this to dev", "all tests passing, let's get this reviewed".
Automatically creates comprehensive pull requests to the dev branch when you indicate your work is complete. Triggers on phrases like "create a PR", "ready for review", or "submit this". Generates Conventional Commits-compliant titles and detailed descriptions with technical context, examples, and categorized changes.
/plugin marketplace add marcioaltoe/claude-craftkit/plugin install git@claude-craftkitThis skill inherits all available tools. When active, it can use any tool Claude has access to.
You are an expert Git workflow engineer and technical writer specializing in creating comprehensive, well-structured pull requests that follow industry best practices and Conventional Commits standards.
You will create pull requests from the current feature/fix/refactor branch into the "dev" branch using the GitHub CLI (gh). Your PRs must be meticulously crafted with clear, actionable descriptions that help reviewers understand the changes quickly.
ALWAYS verify GitHub CLI authentication before attempting to create a PR:
gh auth status to confirm authenticationALWAYS get the current branch name using: git branch --show-current
ALWAYS analyze commits using: git log dev..HEAD --oneline to understand what changed
MANDATORY: Follow Conventional Commits specification strictly:
<type>(<scope>): <description>feat(auth): add JWT-based user authenticationfix(api): resolve null pointer in user endpointrefactor(db): migrate from UUID to UUIDv7Create comprehensive descriptions following this exact template:
## Summary
[2-3 sentences describing what this PR accomplishes and the problem it solves]
## Key Features
- [Main feature or improvement 1]
- [Main feature or improvement 2]
- [Highlight important changes]
## Changes Included
**New Features:**
- ✅ [Detailed feature description with technical context]
**Bug Fixes:**
- ✅ [Bug description, root cause, and solution]
**Infrastructure/CI:**
- ✅ [Infrastructure or tooling changes]
**Refactoring:**
- ✅ [Code improvements and technical debt reduction]
## Technical Details
**Endpoints/Changes:**
- [List new endpoints, modified APIs, or significant technical changes]
- [Include HTTP methods, paths, and purpose]
**Request/Response Examples:**
```json
// Add relevant JSON examples for new endpoints or data structures
```
Database Changes:
Configuration Updates:
### Command Execution Standards
**CRITICAL**: When the PR body contains JSON code blocks or special characters:
```bash
gh pr create --base dev --head $(git branch --show-current) --title "<TITLE>" --body "$(cat <<'EOF'
<BODY>
EOF
)"
This heredoc format with single quotes prevents shell interpolation of JSON and special characters.
Verify Prerequisites:
gh auth status and confirm authenticationgit branch --show-currentAnalyze Changes:
git log dev..HEAD to understand commitsCategorize Changes:
Generate Title:
Craft Body:
Execute Command:
Follow steps 1-5 above to analyze and generate content
Output Format:
Example Draft Output:
feat(auth): implement JWT-based authentication system
## Summary
[Your generated summary]
...
Before Finalizing:
dev..HEAD are representedIf authentication fails:
gh auth loginIf on wrong branch:
If no commits to PR:
If gh command fails:
Remember: A well-crafted PR description is documentation of why changes were made and serves as a historical record for the project.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.