migrate-frontend-forms

Convert legacy JsonForm/FormModel configurations into TanStack-based forms with useScrapsForm or AutoSaveForm.

Updated Apr 1, 2026
One-click install
npx skills add https://github.com/Harigithub11/sentry --skill migrate-frontend-forms-harigithub11
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate-frontend-forms
Source: https://github.com/Harigithub11/sentry/tree/main/.agents/skills/migrate-frontend-forms
Command: npx skills add https://github.com/Harigithub11/sentry --skill migrate-frontend-forms-harigithub11

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migrates legacy JsonForm/FormModel configurations into a modern TanStack-based form system for Sentry settings.

Core Features & Use Cases

  • End-to-end migration of forms used in Settings, including field layout, validation, onSubmit behavior, error handling, and preserving SettingsSearch indexing via FormSearch wrappers.
  • Replacement of old form properties with JSX AppField components and layout-based hints (hintText) to align with new UI patterns.
  • Integration of migration best practices such as onSuccess/onError workflows and automatic/explicit save behaviors, plus updating the generated field registry with extract-form-fields.

Quick Start

Create a new form migration by wrapping migrated fields with FormSearch and replacing JsonForm definitions with useScrapsForm or AutoSaveForm.

Frequently Asked Questions about migrate-frontend-forms

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

FAQPage Schema
How do I migrate legacy JsonForm configurations to a TanStack form system?

Migrating legacy JsonForm configurations to a TanStack form system involves converting old form properties into JSX AppField components and replacing JsonForm definitions with useScrapsForm or AutoSaveForm wrappers.

What is the best way to preserve SettingsSearch indexing when migrating forms?

Preserving SettingsSearch indexing during form migration requires wrapping the migrated fields with FormSearch wrappers to maintain the existing search functionality.

How do I handle validation and onSubmit behavior for migrated TanStack forms?

Handling validation and onSubmit behavior for migrated TanStack forms requires replacing legacy properties with JSX field components, implementing onSuccess/onError workflows, and configuring automatic or explicit save behaviors.

Do I need to update the field registry after migrating FormModel configurations?

Updating the field registry after migrating FormModel configurations is required and is accomplished by running the extract-form-fields script to regenerate the field index.

Can I use AutoSaveForm for end-to-end migration of settings forms?

You can use AutoSaveForm for end-to-end migration of settings forms to replace legacy JsonForm definitions, applying it to manage automatic save behaviors and error handling.