migrate-gitlab-flagslisted
Install: claude install-skill Unleash/unleash-claude-skills
# Migrate GitLab Feature Flags to Unleash (v8+)
Migrate one app or service off GitLab's Unleash-compatible legacy flag API onto a real Unleash v8 server: recreate the flag definitions, rewrite the SDK wiring, and prove behavior parity. There is no automated import/export mechanism from GitLab to Unleash, therefore recreating definitions is always part of the job.
## Non-negotiable invariants
- **State carries over exactly.** A flag enabled in GitLab is enabled in Unleash; a disabled flag arrives disabled (per environment). Always — never ship flags "off for safety" or "on for convenience".
- **Flag names are unchanged** (the only exception: a collision prefix agreed with the user when sharing an OSS `default` project — see Inputs step 3).
- **Minimal code diff.** Mirror the existing patterns; the migration is not a refactoring opportunity (see Phase 5).
- **Least-privilege credentials.** The app gets an Unleash backend/frontend token scoped to its project + environment; the migration itself uses only the access level its provisioning mechanism requires. Never assume an admin token (admin tokens are deprecated by Unleash anyway, so automation uses personal access tokens or service accounts).
## Inputs
1. Resolve `$ARGUMENTS` to the target directory. If empty or ambiguous, ask the user which app/service to migrate before touching anything.
2. Detect the stack from manifests: `package.json`, `go.mod`, `pom.xml` / `build.gradle`, `Gemfile`, `composer.json`, `*.csproj`, `requ