Outfitter Issue
Submit issues to outfitter-dev/outfitter when you discover problems with @outfitter/* packages.
Steps
- Parse input — If
$ARGUMENTS is provided, use it as the issue description to determine type, package, and title.
- Search first — Check for duplicates before creating.
- Classify — Determine issue type (bug, enhancement, docs, dx, unclear-pattern) from context.
- Draft — Dry-run the create script, present the issue for user review.
- Submit — After user approval, run with
--submit.
Before Creating an Issue
Always search first to avoid duplicates:
./scripts/search-issues.sh "keywords describing the issue"
If a similar issue exists, comment on it instead of creating a new one.
Creating an Issue
Use the helper script with --submit to create an issue:
bun ./scripts/create-issue.ts \
--type bug \
--title "Brief description" \
--package "@outfitter/contracts" \
--description "What went wrong" \
--actual "What actually happened" \
--submit
Dry-Run (Default)
Without --submit, the script outputs the gh command for review:
bun ./scripts/create-issue.ts --type bug --title "..." --package "..."
Issue Types
| Type |
When to Use |
Required Fields |
bug |
Something broke |
package, description, actual |
enhancement |
Feature request |
package, description, useCase |
docs |
Documentation gap |
package, description, gap |
dx |
Poor developer experience |
package, description, current |
unclear-pattern |
Confusing guidance |
package, description, context |
For migration-specific feedback, see references/migration-feedback.md.
View Template Requirements
bun ./scripts/create-issue.ts --type bug
Labels
All issues created via this skill get:
- Category label (
bug, feature, documentation, etc.)
feedback — marks it as community feedbacksource/agent — indicates it came from an agent session
Best Practices
- Be specific — include package name, function, and error if known
- Provide context — what task led to discovering this?
- Include workaround — if you found one, share it
- Stay constructive — focus on improvement, not complaint
1---2name: outfitter-issue3description: Submit feedback to the Outfitter team via GitHub issues. Use after discovering bugs, missing features, unclear docs, or improvement opportunities in @outfitter/* packages.4---56# Outfitter Issue78Submit issues to `outfitter-dev/outfitter` when you discover problems with @outfitter/\* packages.910## Steps11121. **Parse input** — If `$ARGUMENTS` is provided, use it as the issue description to determine type, package, and title.132. **Search first** — Check for duplicates before creating.143. **Classify** — Determine issue type (bug, enhancement, docs, dx, unclear-pattern) from context.154. **Draft** — Dry-run the create script, present the issue for user review.165. **Submit** — After user approval, run with `--submit`.1718## Before Creating an Issue1920**Always search first** to avoid duplicates:2122```bash23./scripts/search-issues.sh "keywords describing the issue"24```2526If a similar issue exists, comment on it instead of creating a new one.2728## Creating an Issue2930Use the helper script with `--submit` to create an issue:3132```bash33bun ./scripts/create-issue.ts \34 --type bug \35 --title "Brief description" \36 --package "@outfitter/contracts" \37 --description "What went wrong" \38 --actual "What actually happened" \39 --submit40```4142### Dry-Run (Default)4344Without `--submit`, the script outputs the `gh` command for review:4546```bash47bun ./scripts/create-issue.ts --type bug --title "..." --package "..."48```4950### Issue Types5152| Type | When to Use | Required Fields |53| ----------------- | ------------------------- | ----------------------------- |54| `bug` | Something broke | package, description, actual |55| `enhancement` | Feature request | package, description, useCase |56| `docs` | Documentation gap | package, description, gap |57| `dx` | Poor developer experience | package, description, current |58| `unclear-pattern` | Confusing guidance | package, description, context |5960For migration-specific feedback, see [references/migration-feedback.md](references/migration-feedback.md).6162### View Template Requirements6364```bash65bun ./scripts/create-issue.ts --type bug66```6768## Labels6970All issues created via this skill get:7172- Category label (`bug`, `feature`, `documentation`, etc.)73- `feedback` — marks it as community feedback74- `source/agent` — indicates it came from an agent session7576## Best Practices7778- **Be specific** — include package name, function, and error if known79- **Provide context** — what task led to discovering this?80- **Include workaround** — if you found one, share it81- **Stay constructive** — focus on improvement, not complaint
outfitter-dev