Skill

outfitter-issue

Submit feedback to the Outfitter team via GitHub issues. Use after discovering bugs, missing features, unclear docs, or improvement opportunities in @outfitter/* packages.

Install

npx claudepluginhub outfitter-dev/outfitter --plugin outfitter

Tool Access

This skill is limited to using the following tools:

Bash(gh *)Bash(bun *)Bash(./scripts/*)Read

Preview

Submit issues to `outfitter-dev/outfitter` when you discover problems with @outfitter/\* packages.

Supporting Assets

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.json

SKILL.md

Similar Skills

design-system

Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.

team-skills-platform

163.7k

ui-demo

Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.

team-skills-platform

163.7k

kotlin-patterns

Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.

team-skills-platform

163.7k

Stats

Parent Repo Stars4

Parent Repo Forks1

Last CommitFeb 24, 2026

Actions

View Source View Plugin View on GitHub View README

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 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