القائمة
Submit feedback to the Outfitter team via GitHub issues. Use after discovering bugs, missing features, unclear docs, or improvement opportunities in @outfitter/* packages.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Patterns for @outfitter/daemon including lifecycle management, IPC communication, health checks, and PID files. Use when building background services, daemons, or when "daemon", "IPC", "health check", "background service", or "@outfitter/daemon" are mentioned.
Creates handlers, CLI commands, MCP tools, and daemon services following Outfitter Dev Kit conventions. Use when adding new components to a project, scaffolding code, or when "create handler", "new command", "add tool", or "daemon service" are mentioned.
Deep patterns for @outfitter/mcp including tool registration, Zod schemas, resources, and server configuration. Use when building MCP servers, registering tools, defining resources, or when "MCP server", "MCP tool", "registerTool", or "@outfitter/mcp" are mentioned.
Generates patterns, templates, and guides for @outfitter/* packages. Covers transport-agnostic handler systems, Result types, error taxonomy, and package APIs. Use when working with @outfitter/*, Result types, Handler contract, error taxonomy, or when Result, Handler, ValidationError, NotFoundError, OutfitterError, or package names like contracts, cli, mcp, schema, tui, daemon, config, logging are mentioned.
Verify Outfitter compliance in a codebase. Scans for anti-patterns (throws, console, hardcoded paths) and produces a severity-ranked compliance report. Use for pre-commit checks, code review, or migration validation.
Start with Outfitter — scaffold new projects or adopt patterns in existing codebases. Detects context, scans for adoption candidates, and orchestrates phased conversion.
| name | outfitter-issue |
| version | 0.4.1 |
| description | Submit feedback to the Outfitter team via GitHub issues. Use after discovering bugs, missing features, unclear docs, or improvement opportunities in @outfitter/* packages. |
| allowed-tools | Bash(gh *), Bash(bun *), Bash(./scripts/*), Read |
| user-invocable | true |
| argument-hint | <description of the issue> |
Submit 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 session