Standardized GitHub issue templates for bugs, features, and tasks. Provides title formats, body structure, and required sections. Use when creating issues to ensure consistency. Includes copy-paste templates in templates/ directory.
Provides standardized GitHub issue templates for bugs, features, and tasks with required sections and title formats. Use when creating issues to ensure consistency and completeness.
/plugin marketplace add poindexter12/waypoint/plugin install workflows@waypoint-marketplaceThis skill inherits all available tools. When active, it can use any tool Claude has access to.
templates/bug.mdtemplates/feature.mdtemplates/task.mdStandardized formats for creating GitHub issues with consistent structure.
| Type | Title Prefix | Key Sections |
|---|---|---|
| Bug | bug: | Describe, Expected, Steps, Environment |
| Feature | feat: | Problem, Solution, Alternatives, Acceptance |
| Task | task: or chore: | Description, Checklist, Context |
Title: bug: <short description>
Body:
## Describe the bug
<!-- What happened? -->
## Expected behavior
<!-- What should have happened? -->
## Steps to reproduce
1.
2.
3.
## Environment
- OS:
- Version:
- Relevant config:
## Logs/Screenshots
<!-- If applicable -->
Good:
bug: login fails with expired OAuth tokenbug: dashboard crashes when filter is emptyBad:
bug: it's brokenbug: doesn't workTitle: feat: <short description>
Body:
## Problem
<!-- What problem does this solve? -->
## Proposed solution
<!-- How should it work? -->
## Alternatives considered
<!-- Other approaches you thought of -->
## Acceptance criteria
<!-- How do we know it's done? -->
- [ ] Criterion 1
- [ ] Criterion 2
Good:
feat: add CSV export for reportsfeat: support dark mode in settingsBad:
feat: make it betterfeat: new featureTitle: task: <short description> or chore: <short description>
Use task: for project work, chore: for maintenance/deps/infra.
Body:
## Description
<!-- What needs to be done? -->
## Checklist
- [ ] Step 1
- [ ] Step 2
- [ ] Step 3
## Context
<!-- Why is this needed? -->
Good:
task: set up CI pipelinechore: upgrade React to v19chore: update dependenciesBad:
task: do the thingchore: stuffIs something broken?
YES → Bug Report
NO → Continue
Is this new functionality?
YES → Feature Request
NO → Continue
Is this maintenance/infrastructure?
YES → Task (chore:)
NO → Task (task:)
See templates/ for copy-paste ready files:
bug.md - Bug report templatefeature.md - Feature request templatetask.md - Task/chore templateAfter using this skill to create an issue, use:
gh issue creategh-issue-triage - Labeling and prioritization rulesgh-issue-lifecycle - State transitions and linkinggh-wrangler - Interactive issue managementThis 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.