Enforce 1 PR = 1 Jira Issue workflow for clean project tracking
Enforces 1 PR = 1 Jira issue workflow by creating dedicated branches for each issue. Claude uses this when starting work with `/jira:start` to ensure clean project tracking and focused PRs.
/plugin marketplace add minukHwang/claude-plugins/plugin install workflow@minukHwang-pluginsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Maintain clean project tracking by ensuring each Pull Request maps to exactly one Jira issue.
Each Jira issue gets its own dedicated branch.
# Correct
feature/CP-1-add-authentication
feature/CP-2-fix-login-bug
# Incorrect
feature/CP-1-CP-2-mixed-work # Multiple issues in one branch
Each branch produces exactly one Pull Request.
# Correct workflow
/jira:start CP-1 # Creates feature/CP-1-description
# ... work ...
/jira:done # Creates PR for CP-1 only
# Incorrect
# Working on multiple issues before creating PR
If a new task comes up while working on an issue:
# Currently on feature/CP-1-add-auth
git stash # Save current work
/jira:start CP-2 # New branch: feature/CP-2-new-task
# ... complete CP-2 work ...
/jira:done # Create PR for CP-2
git checkout feature/CP-1-add-auth
git stash pop # Resume CP-1 work
/jira:start CP-1
This:
feature/CP-1-description/git:commit
This:
[CP-1] prefix/jira:done
This:
# Currently on feature/CP-1-add-dashboard
git stash # Save incomplete work
/jira:create # Create bug issue (CP-5)
/jira:start CP-5 # Switch to bugfix/CP-5-fix-crash
# ... fix bug ...
/git:commit # Commit fix
/jira:done # Create PR, update status
git checkout feature/CP-1-add-dashboard
git stash pop # Resume dashboard work
For very small fixes (< 5 minutes), you can:
Never mix issues in commits.
All commits should reference the current issue:
[CP-1] Add user authentication flow
[CP-1] Fix login button styling
[CP-1] Add unit tests for auth service
The /git:commit command handles this automatically when Jira is configured.
If you see commits like:
[CP-1] Add feature
[CP-2] Fix bug # Wrong! Different issue
[CP-1] Continue feature
Solution: Create separate PR for CP-2 work.
Branches with 10+ commits or 3+ days of work may indicate:
/git:pr will warn if multiple issue keys are detected in commits:
⚠️ Warning: Multiple issue keys detected!
Branch: CP-1
Commits reference: CP-1, CP-2, CP-3
Best practice: 1 PR = 1 Issue
Continue anyway? [Y/n]
| Metric | Before | After |
|---|---|---|
| PR review time | Long, unfocused | Short, targeted |
| Issue tracking | Scattered | Clear |
| Rollback scope | Large, risky | Small, safe |
| Code review | Confusing | Straightforward |
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.
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.
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.