Submit feedback to the Outfitter team via GitHub issues. Use after discovering bugs, missing features, unclear docs, or improvement opportunities in @outfitter/* packages.
Creates GitHub issues for Outfitter package feedback after checking for duplicates.
npx claudepluginhub outfitter-dev/outfitterThis skill is limited to using the following tools:
references/migration-feedback.mdscripts/create-issue.tsscripts/search-issues.shtemplates/bug.jsontemplates/compatibility.jsontemplates/conversion-helper.jsontemplates/docs.jsontemplates/dx.jsontemplates/enhancement.jsontemplates/index.tstemplates/migration-docs.jsontemplates/migration-pattern.jsontemplates/unclear-pattern.jsonSubmit issues to outfitter-dev/outfitter when you discover problems with @outfitter/* packages.
$ARGUMENTS is provided, use it as the issue description to determine type, package, and title.--submit.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.
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
Without --submit, the script outputs the gh command for review:
bun ./scripts/create-issue.ts --type bug --title "..." --package "..."
| 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.
bun ./scripts/create-issue.ts --type bug
All issues created via this skill get:
bug, feature, documentation, etc.)feedback — marks it as community feedbacksource/agent — indicates it came from an agent sessionYou MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.