Use when creating, reviewing, or merging pull requests. Includes CI checks, review requirements, and merge approval rules.
/plugin marketplace add sharpner/claude-agents/plugin install workflow-core@sharpner-claude-agentsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
NEVER MERGE YOURSELF - ALWAYS WAIT FOR USER APPROVAL!
# Run quality checks
npm test # or: go test ./...
npm run build # or: go build ./...
npm run lint # or: golangci-lint run
gh pr create --title "type: description (closes #issue)" --body "..."
gh pr checks <pr-number> --watch
gh pr view <pr-number> --json reviews --jq '.reviews[] | select(.state == "APPROVED")'
IF NO APPROVAL -> STOP AND WAIT!
gh pr merge <pr-number> --squash --delete-branch
| Verdict | Action |
|---|---|
| PASS | Can be merged |
| NEEDS WORK | DO NOT merge! Fix first! |
| FAIL | DO NOT merge! Blocker! |
type: short description (closes #issue)
Types:
- feat: New feature
- fix: Bug fix
- refactor: Code refactoring
- docs: Documentation
- test: Adding tests
- chore: Maintenance
## Summary
- What changed and why
## Test Plan
- [ ] Unit tests added/updated
- [ ] Manual testing completed
- [ ] Edge cases verified
## Checklist
- [ ] Code follows project standards
- [ ] Tests pass (100% green)
- [ ] No TODOs in code
- [ ] Documentation updated (if needed)
| Label | When to Use |
|---|---|
in progress | Actively working on issue |
blocked | Waiting on dependency |
ready for review | PR created, awaiting review |
# Add label
gh issue edit <nr> --add-label "in progress"
# Add blocker comment
gh issue comment <nr> --body "Blocked by #<dependency> - [reason]"
"Quality gates exist for a reason."
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.