Skill654 estrellas del repoactualizado today

vellum-feature-flag-rollout

This skill guides code review and implementation of feature flags for the Vellum Assistant. Use it when adding, editing, or reviewing assistant feature flags, rollout-gated behavior, release-note handling, permission controls, or related platform infrastructure changes. The skill ensures proper registry declaration, safe defaults, test coverage, and hygiene of user-facing communications to prevent accidentally shipping incomplete features to end users.

Ver fuente Repositorio: vellum-assistant

Instalar en Claude Code

Copiar

git clone --depth 1 https://github.com/vellum-ai/vellum-assistant /tmp/vellum-feature-flag-rollout && cp -r /tmp/vellum-feature-flag-rollout/.cursor/skills/vellum-feature-flag-rollout ~/.claude/skills/vellum-feature-flag-rollout

Después abre una sesión nueva de Claude Code; el skill carga automáticamente.

Definición

SKILL.md

# Vellum Feature Flag Rollout

## Flag Rules

Assistant feature flags use simple kebab-case keys and must be declared in:

```text
meta/feature-flags/feature-flag-registry.json
```

New flags require:

- `scope: "assistant"`
- a canonical kebab-case key
- a safe default
- tests or guard coverage when resolver behavior changes
- a companion `vellum-assistant-platform` PR to provision the flag in Terraform

## Rollout Hygiene

There is no release-note surfacing mechanism — the workspace-bulletin feature was removed and the historical release-note migrations are frozen. Do not add new release-note migrations for any feature (flagged or GA). If a release needs user-facing notes, design an explicit on-demand surfacing mechanism first.

## Permission Controls V2

Under `permission-controls-v2`, do not add new deterministic approval modes for assistant-owned actions beyond the conversation-scoped host computer access gate. Avoid global toggles, persistent trust-rule UI, wildcard scopes, and time-window approvals.

## Review Workflow

1. Confirm whether the change adds, renames, removes, or consumes a flag.
2. Check registry declaration and key format.
3. Check default behavior and rollout safety.
4. Check docs, release notes, and user-facing copy for flag leaks.
5. Check whether the platform repo needs a Terraform update.
6. Recommend focused tests for resolver, route, UI, or behavior changes.

## PR Notes

Call out:

- flag key
- default state
- rollout plan
- companion platform PR status
- whether release notes are intentionally omitted

Del mismo repositorio

vellum-boundary-guardSkill

Check Vellum Assistant architecture and package boundaries. Use when editing imports, moving code, adding endpoints, touching assistant/gateway/client/skill boundaries, or reviewing architecture-sensitive changes.

vellum-change-reviewSkill

Review Vellum Assistant code changes for correctness, repo-specific quality rules, security risks, and missing validation. Use when reviewing diffs, preparing a PR, finishing implementation work, or when the user asks for a code review, quality pass, or pre-merge check in this repository.

vellum-migration-checklistSkill

Validate Vellum Assistant database and workspace migrations. Use when adding, editing, reviewing, or testing migrations, release-note migrations, persisted schemas, workspace file formats, or data backfills.

vellum-pr-readinessSkill

Prepare Vellum Assistant branches for review by checking git hygiene, PR scope, tests, docs, migrations, Linear linking, and companion repo needs. Use before creating a pull request, splitting work into PRs, or asking whether a branch is ready.