feature-flags
Gate a Sentry feature behind a FlagPole feature flag. Use when adding a feature flag, registering a flag in temporary.py, checking a flag from Python or the frontend, enabling a flag in tests, or asking where FlagPole rollout config lives. Trigger on "add a feature flag", "gate this behind a flag", "register a flag", "features.has", "api_expose", "OrganizationFeature", "ProjectFeature", "FlagPole".
Install
With your agent
Install OMGSkills skill "getsentry/sentry:.agents/skills/feature-flags" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/getsentry/sentry /tmp/sentry && ln -s /tmp/sentry/.agents/skills/feature-flags ~/.claude/skills/feature-flagsFrom README
Feature Flags (FlagPole) New features should be gated behind a feature flag. Register the flag in src/sentry/features/temporary.py: Use apiexpose=True if the frontend needs to check the flag. Use ProjectFeature and a projects: prefix for project-scoped flags. Python check: Frontend check (requires apiexpose=True): Tests: Rollout: FlagPole YAML config lives in the sentry-options-automator repo, not here. Removal: once the rollout is finished, the flag comes out in a fixed three-PR order — see the remove-option-or-flag skill. See https://develop.sentry.dev/feature-flags/ for full docs.
More from this repo
design-system
Guide for using Sentry's layout and text primitives.
backend-conventions
Sentry backend conventions for logging, tracing/spans, span/tag attribute naming, metrics tags, and the options system.
generate-frontend-forms
Guide for creating forms using Sentry's new form system.