stack-feedback_skill

Overview

This skill creates GitHub issues on outfitter-dev/outfitter for problems discovered while using @outfitter/* packages. It standardizes issue content, labels, and origin metadata so feedback is actionable and traceable. Use it to report bugs, request features, clarify docs, or suggest ergonomics improvements.

How this skill works

The helper script builds validated issue bodies, selects labels based on category, and detects the git origin to include a "Discovered In" link. By default it performs a dry run that prints the gh command JSON; passing --submit will call the GitHub CLI to create the issue. Templates expose required and optional fields per issue type to ensure consistent, useful reports.

When to use it

• You encounter a bug in an @outfitter package
• A missing feature or helper would improve developer experience
• Documentation is unclear or omits edge cases
• You find a pattern gap or migration guidance is missing
• Error messages or ergonomics make tasks harder than expected

Best practices

• Be specific: include package, function, and code snippets or lines when possible
• Provide context: describe the task and steps to reproduce the problem
• Include the actual behavior and an expected outcome or workaround
• Check existing issues to avoid duplicates and link related issues
• Use the script templates to supply required fields for each issue type

Example use cases

• Report a runtime error in @outfitter/contracts with steps and stack trace
• Request an enhancement like a Result.tap helper with a concrete use case
• Open a docs issue for a missing handler contract edge case
• Submit a migration-pattern issue describing a problematic upgrade scenario
• Batch-create and cross-reference a set of ergonomics and conversion-helper issues