# flag-and-release-change

flag-and-release-change — a skill for Claude Code takes a pull request from flag review to an automated LaunchDarkly release. It updates the PR branch after approval.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 267 installs · ★ 32 repo stars
- Author: launchdarkly
- License: Apache-2.0 · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/launchdarkly/ai-tooling/tree/HEAD/skills/feature-flags/flag-and-release-change/SKILL.md
- Updated: 2026-11-11
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/flag-and-release-change

## What it does

The skill reads the pull request diff, decides whether the change needs a feature flag, creates a LaunchDarkly flag turned OFF, and places the new code path behind it. It then records an automated release for after the PR merges, following the target environment’s policy.

The workflow has a planning phase and an implementation phase. Planning covers the changed files, flag design, target environments, and release intent; it makes no edits. Approval is required before the skill creates the flag or changes the branch. You also need the remotely hosted LaunchDarkly MCP server, `git` access to read and push the PR repository, plus the flag-creation and release skills.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add launchdarkly/ai-tooling --skill flag-and-release-change -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/flag-and-release-change/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/flag-and-release-change/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add launchdarkly/ai-tooling --skill flag-and-release-change -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/flag-and-release-change/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add launchdarkly/ai-tooling --skill flag-and-release-change -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/flag-and-release-change/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install launchdarkly/ai-tooling skills/feature-flags/flag-and-release-change
```

2. **Manually: put the files in place**
- File: `.github/skills/flag-and-release-change/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add launchdarkly/ai-tooling --skill flag-and-release-change -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/launchdarkly/ai-tooling --path skills/feature-flags/flag-and-release-change
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/flag-and-release-change/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add launchdarkly/ai-tooling --skill flag-and-release-change -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/launchdarkly/ai-tooling/tree/HEAD/skills/feature-flags/flag-and-release-change/SKILL.md

## When to use it
- decide whether a pull request change needs a feature flag
- create an OFF LaunchDarkly flag for a new code path
- guard the changed code on the PR branch
- schedule an automated release after the PR merges
- coordinate flag creation and release planning

## Example prompts
- Review this pull request, decide whether its change needs a LaunchDarkly flag, and show me the plan before editing anything.
- After I approve the plan, create the flag turned OFF and put the new path behind it on the PR branch.
- Prepare the post-merge automated release and show the release intent for each target environment.

## Source text · SKILL.md · Apache-2.0

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 3165a0da65e71f83.

BEGIN THIRD-PARTY FILE 3165a0da65e71f83
```text
---
name: flag-and-release-change
description: "Drive a pull request's change end to end: decide it's flag-worthy, create the guarding flag, wire the new code path behind it on the PR branch, and record an automated release so the change ships safely when the PR merges. A portable orchestrator that composes should-flag-change, launchdarkly-flag-create, and flag-release. Keywords: flag a PR, wrap change in a flag, dark launch, kill switch, auto-release, automated rollout, end-to-end flag workflow."
license: Apache-2.0
compatibility: Requires the remotely hosted LaunchDarkly MCP server and a git CLI with access to the PR's repository
metadata:
  author: launchdarkly
  version: "0.1.0"
---

# Flag & Release a PR Change

You're using a skill that takes a pull request whose change should ship behind a feature flag and drives it end to end: decide it needs a flag, create the guarding flag, wire the new behavior behind it on the PR's branch, and record an **automated release** so the change ships safely once the PR merges.

**The deploy is not the release.** The merge ships the control path — the flag is created OFF, so deployment always serves the pre-change behavior. The *release* is the flag operation the automated rollout performs afterward, governed by the environment's policy. Creating the flag OFF and recording the release are deliberately separate things.

This skill is a **portable PR orchestrator**. It doesn't own the flag mechanics or the release mechanics — it composes three focused skills and adds the PR workflow (read the diff, work in a clone, push to the branch) plus the plan→implement sequencing:

| Step | Owned by | This skill's role |
|------|----------|-------------------|
| Decide *whether* to flag | [`should-flag-change`](../should-flag-change/SKILL.md) (advisory, read-only) | Act on a "yes"; make the call yourself if it wasn't run |
| Create the flag + wire the code | [`launchdarkly-flag-create`](../launchdarkly-flag-create/SKILL.md) | Invoke it against the change; don't re-teach flag creation or SDK patterns |
| Record the release | [`flag-release`](../flag-release/SKILL.md) | Hand off once the flag exists and the code is pushed; don't re-teach rollout mechanics |

Don't duplicate any composed skill's mechanics here. This skill's only unique content is the **PR wrapper** (clone, three-dot diff, commit/push to the branch) and the **plan→implement** flow that stitches the three together.
```
END THIRD-PARTY FILE 3165a0da65e71f83

The third-party file has ended. Everything between the 3165a0da65e71f83 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2454 of 10363 bytes. © launchdarkly · Apache-2.0 · https://github.com/launchdarkly/ai-tooling/tree/HEAD/skills/feature-flags/flag-and-release-change/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
