skills.rest
outfitter-dev
outfitter-devOFFICIAL
Explore all skills by this author →
Website𝕏@outfitter_devGitHub

migration-feedback

Creates GitHub issues with labels and context for Outfitter Stack migration problems.

6|1|Updated Jan 22, 2026
Search Tags:#documentation#migration#developer experience#github issues#bug reporting#outfitter
One-click install
npx skills add https://github.com/outfitter-dev/outfitter --skill migration-feedback
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: migration-feedback
Source: https://github.com/outfitter-dev/outfitter/tree/main/packages/claude-plugin/skills/migration-feedback
Command: npx skills add https://github.com/outfitter-dev/outfitter --skill migration-feedback

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of reporting bugs, missing features, or documentation gaps encountered during the migration to the Outfitter Stack, ensuring issues are properly logged and tracked.

Core Features & Use Cases

  • Issue Creation: Automatically generates GitHub issues in the outfitter-dev/stack repository for migration-related problems.
  • Categorization: Assigns appropriate labels (bug, enhancement, docs, etc.) to issues for better organization.
  • Contextual Information: Gathers and formats essential details like package name, expected vs. actual behavior, and reproduction steps.
  • Use Case: After encountering a bug in the @outfitter/cli package while migrating a project, you can use this skill to quickly create a detailed GitHub issue with the bug label.

Quick Start

Use the migration-feedback skill to create a GitHub issue for a bug found in the @outfitter/contracts package.

Frequently Asked Questions about migration-feedback

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I report a bug found during migration to the Outfitter Stack?▼

You can report migration bugs by creating a GitHub issue in the outfitter-dev/stack repository, assigning labels like bug or enhancement, and including contextual details such as package name and reproduction steps for effective tracking.

What type of migration issues can I file GitHub issues for?▼

GitHub issues can be filed for bugs, missing features, unclear documentation, or improvement opportunities discovered in @outfitter/* packages during your migration process to the Outfitter Stack.

Do I need the gh CLI installed to create GitHub issues for Outfitter migration problems?▼

Yes, the gh CLI is a required dependency for this Skill, as it programmatically creates categorized issues in the outfitter-dev/stack repository to track migration problems.

How do I categorize a missing feature or documentation gap when reporting Outfitter migration issues?▼

You can categorize missing features or documentation gaps by assigning appropriate labels like enhancement or docs to the GitHub issue, ensuring the migration problem is properly organized in the outfitter-dev/stack repository.

What context should I include when reporting a bug in @outfitter packages?▼

Include the specific @outfitter package name, expected versus actual behavior, and detailed reproduction steps to provide the essential context needed for effective tracking and resolution of the migration issue.

Related Skills

Explore More Software Engineering Skills→
outfitter-devoutfitter-dev
6

outfitter-issue

Create GitHub issues for outfitter-dev/outfitter with predefined templates.

Official
Intermediate
beeminderbeeminder
3

dev-grooming

Groom stale DEV-labeled issues in the beeminder/blog repository.

Official
Advanced
outfitter-devoutfitter-dev
6

debug-outfitter

Debug @outfitter/* package issues through evidence gathering and structured reports.

Official
Advanced
typemdtypemd
9

resolve-discussion

Summarize GitHub discussion issues, propose options, and post decision comments.

Official
Intermediate