v0.x-to-pack-starter-split

Migrate stripe, twilio, and clerk-webhook code from Forge packs to starter-owned files.

4|1|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/reliant-labs/forge --skill v0-x-to-pack-starter-split
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: v0.x-to-pack-starter-split
Source: https://github.com/reliant-labs/forge/tree/main/internal/templates/project/skills/forge/migration/v0.x-to-pack-starter-split
Command: npx skills add https://github.com/reliant-labs/forge --skill v0-x-to-pack-starter-split

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you migrate stripe, twilio, and clerk-webhook business-integration code when upgrading Forge across the version where those components were demoted from regen-prone packs to user-owned one-time-copy starters.

Core Features & Use Cases

  • Detect whether your project was affected by checking whether forge.yaml lists stripe, twilio, or clerk-webhook under packs: or by using Forge audit signals that packs are missing from the registry.
  • Safely migrate the project-owned boundary by removing the affected items from packs: and re-pulling starter templates via forge starter add with the correct --service value.
  • Stabilize future forge generate runs so your customized business logic in pkg/clients/... (and pkg/clerk/webhook.go for clerk-webhook) stops being overwritten and becomes idempotent going forward.

Quick Start

Use the skill to migrate stripe, twilio, and clerk-webhook by removing them from the forge.yaml packs: list and then running forge upgrade (or re-running forge starter add stripe --service <svc> / forge starter add twilio --service <svc> / forge starter add clerk-webhook --service <svc>) followed by forge generate to verify no more pack regeneration diffs occur.

Frequently Asked Questions about v0.x-to-pack-starter-split

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

FAQPage Schema
Why does forge generate keep overwriting my custom Stripe and Twilio code in pkg/clients?

Stripe, Twilio, and Clerk webhook integrations listed under packs in forge.yaml trigger continuous pack regeneration, overwriting your custom business logic in pkg/clients during every generate run.

How do I migrate Stripe and Twilio integrations from Forge packs to starter-owned files?

Remove stripe, twilio, or clerk-webhook from the packs list in forge.yaml, then re-scaffold them using forge starter add with the correct --service value to copy starter templates into your project.

How do I know if my Forge project is affected by the pack to starter migration?

Check whether forge.yaml lists stripe, twilio, or clerk-webhook under the packs section, or use Forge audit signals indicating the registry no longer provides the corresponding pack templates for those components.

What should I do after migrating clerk-webhook from packs to starters in Forge?

Re-run forge generate after removing clerk-webhook from packs and re-scaffolding via forge starter add to verify idempotency and confirm no further pack regeneration diffs overwrite your custom webhook logic.

Can I keep my customized business logic in pkg/clerk/webhook.go when upgrading Forge?

Customized business logic in pkg/clerk/webhook.go is preserved by migrating clerk-webhook from a Forge pack to a starter-owned file, which stops forge generate from overwriting your changes on subsequent runs.