Skip to content

Add "Feature Flag Audit and Cleanup Agent" check#3

Open
continue[bot] wants to merge 1 commit into
mainfrom
add-check/feature-flag-audit-and-cleanup-agent
Open

Add "Feature Flag Audit and Cleanup Agent" check#3
continue[bot] wants to merge 1 commit into
mainfrom
add-check/feature-flag-audit-and-cleanup-agent

Conversation

@continue
Copy link
Copy Markdown
Contributor

@continue continue Bot commented May 17, 2026

Adds the Feature Flag Audit and Cleanup Agent check to this repository.

This check will be synced from .continue/checks/feature-flag-audit-and-cleanup-agent.md and can be customized by editing the file directly.


Opened via Continue Hub

Summary by Sourcery

Add a configurable Feature Flag Audit and Cleanup Agent check for PostHog feature flags to the repository.

New Features:

  • Introduce a Feature Flag Audit and Cleanup Agent check definition synced from the .continue configuration.

Documentation:

  • Document the agent’s purpose, triage criteria, GitHub issue and audit templates, commit message format, and scheduling/success metrics for feature flag maintenance.

@sourcery-ai
Copy link
Copy Markdown

sourcery-ai Bot commented May 17, 2026

Reviewer's Guide

Adds a new Continue AI check configuration for a "Feature Flag Audit and Cleanup Agent" that audits PostHog feature flags, classifies them, and generates standardized GitHub issues and summaries for cleanup work.

Flow diagram for feature flag triage decision tree

flowchart TD
  A[100% rollout for 90+ days?]
  A -->|Yes| B[Ready for Removal]
  A -->|No| C[Modified in last 120 days?]

  C -->|No| D[Rollout <50%?]
  D -->|Yes| E[Stale Experimental]

  C -->|Yes| F[5+ targeting rules?]
  F -->|Yes| G[Complex Targeting]
  F -->|No| H[Performance issues?]

  H -->|Yes| I[Performance Impact]
  H -->|No| J[No code refs?]
  J -->|Yes| K[Cleanup Required]
Loading

File-Level Changes

Change Details Files
Introduce a new Feature Flag Audit and Cleanup Agent check configuration for Continue/PostHog.
  • Define a check named "Feature Flag Audit and Cleanup Agent" that uses built-in and posthog/posthog-mcp tools.
  • Document multi-phase execution steps for discovering feature flags, classifying them based on lifecycle and risk, and creating GitHub issues via the gh CLI.
  • Provide structured templates for individual flag issues, overall audit summaries, and commit messages to standardize flag cleanup work.
  • Specify the mapping and purpose of PostHog MCP tools, required GitHub labels, audit cadence, and success metrics for ongoing feature-flag hygiene.
.continue/checks/feature-flag-audit-and-cleanup-agent.md

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

Copy link
Copy Markdown

@sourcery-ai sourcery-ai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey - I've left some high level feedback:

  • The label placeholder [priority] in the gh issue create command doesn’t match the concrete labels listed later (high-priority, medium-priority); consider standardizing the exact label names to avoid inconsistent labeling by the agent.
  • In the "PostHog MCP Tools" section, the tool names are listed without the mcp__posthog__ prefix used in the execution steps; aligning these names (or explicitly clarifying the mapping) would make it easier to implement the agent correctly.
Prompt for AI Agents
Please address the comments from this code review:

## Overall Comments
- The label placeholder `[priority]` in the `gh issue create` command doesn’t match the concrete labels listed later (`high-priority`, `medium-priority`); consider standardizing the exact label names to avoid inconsistent labeling by the agent.
- In the "PostHog MCP Tools" section, the tool names are listed without the `mcp__posthog__` prefix used in the execution steps; aligning these names (or explicitly clarifying the mapping) would make it easier to implement the agent correctly.

Fix all in Cursor


Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants