Outfitter Feedback
Submit issues to outfitter-dev/outfitter when you discover problems with @outfitter/* packages.
Before Creating an Issue
Always search first to avoid duplicates:
bash
./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:
bash
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:
bash
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
bash
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 feedback - •
source/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