Automatically add PostHog analytics instrumentation to code. Triggers when user asks to add tracking, instrument events, add analytics, or implement feature flags in their codebase.

2026-05-0144

nuqs

neplextech/yasumu

nuqs (type-safe URL query state) best practices for Next.js applications. This skill should be used when writing, reviewing, or refactoring code that uses nuqs for URL state management. Triggers on tasks involving useQueryState, useQueryStates, search params, URL state, query parameters, nuqs parsers, or Next.js routing with state.

2026-05-0144

name	Review Changes
description	Perform a structured code review using change detection and impact

Review Changes

Perform a thorough, risk-aware code review using the knowledge graph.

Steps

Run detect_changes to get risk-scored change analysis.
Run get_affected_flows to find impacted execution paths.
For each high-risk function, run query_graph with pattern="tests_for" to check test coverage.
Run get_impact_radius to understand the blast radius.
For any untested changes, suggest specific test cases.

Output Format

Provide findings grouped by risk level (high/medium/low) with:

What changed and why it matters
Test coverage status
Suggested improvements
Overall merge recommendation

Token Efficiency Rules

ALWAYS start with get_minimal_context(task="<your task>") before any other graph tool.
Use detail_level="minimal" on all calls. Only escalate to "standard" when minimal is insufficient.
Target: complete any review/debug/refactor task in ≤5 tool calls and ≤800 total output tokens.