Setting the file. One moment.
Chapter 26 · Flag And Release Change
Subchapter 26.3
README.mdMarkdown2 KBView on GitHub
A portable Agent Skill that drives a pull request’s change end to end: decide it needs a flag, 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.
This skill is a PR orchestrator. It composes three focused skills and adds only the PR workflow (clone, three-dot diff, commit/push to the branch) and the plan→implement sequencing:
| Step | Owned by |
|---|---|
| Decide whether to flag | should-flag-change (advisory, read-only) |
| Create the flag + wire the code | launchdarkly-flag-create |
| Record the release | flag-release |
The deploy is not the release: the merge ships the control path (flag OFF); the release is the flag operation the recorded rollout performs afterward. An automation harness can bypass this skill and invoke the three composed skills directly — this is the portable, human-in-the-loop path.
Copy skills/feature-flags/flag-and-release-change/ into your client’s skills path, along with the composed skills it delegates to.
git CLI that can read and push to the PR’s repository.launchdarkly-flag-create and flag-release.This PR should ship behind a flag — create it, wire it on the branch, and set up
the release. Hold production until next week.flag-and-release-change/
├── SKILL.md
├── marketplace.json
├── README.md
└── references/
└── pr-wiring.mdApache-2.0